nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bit datatype and cached tables

boggle

Hi, we are just now getting around to enabling Teamsite search, eventsubsystem, ... and are planning to use Oracle 9i [Teamsite 6.7.2, OD 6.2 on Windows platform]. It was proposed that we put the OD Scheduler info into Oracle too. I read the Schedule DB Schema for Oracle post with interest. My first question is what modifications folks have made to accommodate the BIT datatype used by STARTDEPLOY in tables IWOV_SCHEDULE and IWOV_QUEUE as Oracle does not support boolean datatypes? Any best practices?

The second question pertains to archiving. Is anyone using Oracle for the archiving instead of hsql? If so did you have to modify the hsql script (archiveDB_hSql.sql), specifically: CREATE CACHED TABLE, as cached doesn't necessarily mean the same thing in Oracle.

PS, anyone using Oracle 11g? We just got word that our database group is planning to skip 10g and go straight to 11g (probably by this fall).

Thank You

Find more posts tagged with

Comments

Firenze

I have seen problems with ODAdmin not reconnecting to the Oracle DB for scheduling when the DB connection breaks. ODAdmin had to be reset when this was detected. So, you should include testing for that condition with your setup if you go with Oracle.

boggle

Thank you for that good suggestion!

Also, by trying to open a ticket on the subject I was finally presented with an article (which did not come up when I had searched knowledge base myself prior to posting here

) with the solution for bit datatype:

For the script to work in Oracle, you need to change the occurrences of BIT data type to NUMBER(1).