Troubleshooting with Oracle Database
Resolve the errors that you may come across while configuring the Oracle database.
| Issue | Description | Solution |
|---|---|---|
| Bad Interpreter Issue | A “bad interpreter” error is displayed on UNIX. | The first line of all scripts on UNIX must be as follows: #!/usr/bin/sh
Check whether or not the first line of the UNIX script follows this format. You can also create a soft link as follows: |
| Insufficient Shared Memory Issue |
Oracle database error, unable to allocate required shared memory. ( |
This error is related to the insufficient shared pool size allocation. Consult Oracle documentation and your DBA to resolve it. Usually the error may be resolved by increasing the amount of available shared memory. |
| Inserting and Updating Data from ProcessLog and ProcessState Tables |
Two errors are intermittently thrown when inserting or updating data from ProcessLog and ProcessState tables, even though the data to be inserted has a valid value and length. This error has been observed on Oracle 10.1.0.2.0.
|
Restarting the application server might resolve the issue temporarily.
There are similar issues reported in Oracle MetaLink. Reference Document IDs: 241358.1, 461670.1 If the problem persists, contact Oracle support and consider upgrading to the latest patch. |
| Seed data errors for exceeded length |
After you change the value of the SQL>CREATE INDEX WORKITEMDETAIL_IDX1 ON WORKITEMDETAIL ( NAME, Value ) TABLESPACE VELODBINDX1 SQL>CREATE INDEX FSENTRY_IDX ON FSENTRY ( PATH ASC, NAME ASC ) TABLESPACE VELODBINDX1 SQL>CREATE INDEX SFSENTRY_IDX ON SFSENTRY ( PATH ASC, NAME ASC ) TABLESPACE VELODBINDX1 |
To fix this issue, run the upgradeAttributeLength.sql script located at $MQ_HOME/db/DatabaseType/install/scripts/utility. |