Network Issue
If there is no network connectivity to the database server, users will get this error message.
Oracle is down or frozen
1. Determine if database is up.
A. sql
B. If SQL> appears, database is up.
C. If no SQL> appears, an Oracle error will appear.
2. If database is not up, then attempt to restart it and application.
A. Application should be stopped if it is running.
1. appcontrol
2. Select option to Shut Down Application
B. Shut down Oracle.
1. sqlplus /nolog
2. conn / as sysdba
3. shutdown immediate
4. Wait for Oracle to shutdown.
C. Start up Oracle.
1. startup
2. Wait for Oracle to start up.
3. exit
D. Login UNIX and start application.
1. appcontrol
2. Select option to Start Up Application
E. Retry logging into Client and RDT's.
3. If the database appears to be up but you cannot log in to sqlplus, it could be that Oracle
is hung up or in a "frozen" state.
A. Check if archive logs directory filled up to 100% capacity.
1. Determine archive directory: dbstruct |more
2. Press space bar twice to page through display.
Example:
Getting dump destinations...
Archive /oracle/archredo/dcs
Audit /oracle/admin/dcs/audit
Background /oracle/admin/dcs/bdump
Core /oracle/admin/dcs/cdump
User /oracle/admin/dcs/udump
3. Check disk space: df -k
4. If Oracle archive log is full; 100% used, need to manually move some of the archive logs to a
different mount point or disk. Cannot run the backup if disk space is at 100% used.
5. Go to above directory; example: cd /oracle/archredo/dcs
6. Display files: ls -ltr | pg
7. Move files to free up space: mv [File Name] [Path Name]
B. If Oracle archive directory is full, check if backup failed. If so, rerun backup. See Article 32316.
C. Making drastic changes to purge settings could result in large amounts of archive logs
being written. See purge information listed below.
D. If the backup did not fail, and you notice that there are large quantities of archive logs
being written to disk at a very fast pace, contact JDA Support to run an Oracle Log
Miner to determine what SQL is causing archive logs to fill up.
Purge
If considering making changes to purge settings, it is recommended that you change purge options to only allow the purge daemon to purge a few days worth of records at a time. For example, if current option is set to keep 180 days worth of data, it would not be recommended to change that setting to 90 days overnight. Then the system would have to purge 90 days worth of data which could result in archive logs filling up the disk. It would be better to decrease purge days in smaller increments. For example, on the first night change setting to 160, then on next night change setting to 140, etc. This will allow archive logs to be purged by the backup script every night so the chances of filling up the disk will be much less.
If there have been recent changes to purge settings (i.e. "purge days" setting has decreased), try stopping the purge daemon to determine if that stops the archive logs from being written:
1. Check to see if the purge is running:
A. Display purge daemon process: pu |grep purdae
2. Stop the purge daemon: telsia stop purdae
3. Readjust purge settings so that they are closer to the original setting.
A. From Client, select Administration, System Options, Purge Days Tab
4. Run a backup to remove some of old archive logs or manually move some logs to different mount
point or directory. See step 3A above. Note: DO NOT remove archive logs! They are used to
recover your database.
5. Once the purge settings have been readjusted, restart the purge daemon.
A. Start purge daemon: telsia start purdae
B. Display purge daemone process: pu | grep purdae
Example:
dcsdba 7923 7849 0 May13 ? 00:00:16 purdae -t 23
dcsdba 21098 20627 0 15:16 pts/2 00:00:00 grep purdae
|
