Home » RDBMS Server » Enterprise Manager » Database Hangs for Cold Backup (oracle 11gR2, OEM 12cr5)
Database Hangs for Cold Backup [message #654483] Wed, 03 August 2016 14:15 Go to next message
krish96
Messages: 70
Registered: October 2012
Member
Hello Experts,

we have a database which is set for cold backup every night incr and weekly full backups.. everything was fine until we added OEM agent .. It hangs during cold backup and couldn't run shutdown immediate command ..if we delete the target from OEM than the database cold backups runs as expected ..

Please let me know if you have any information on this issue..

Thank you in advance..
Re: Database Hangs for Cold Backup [message #654485 is a reply to message #654483] Wed, 03 August 2016 14:27 Go to previous messageGo to next message
BlackSwan
Messages: 25745
Registered: January 2009
Location: SoCal
Senior Member
What clues exists within alert_SID.log file?
Re: Database Hangs for Cold Backup [message #654486 is a reply to message #654485] Wed, 03 August 2016 15:07 Go to previous messageGo to next message
krish96
Messages: 70
Registered: October 2012
Member
here's the log

hutting down instance (immediate)
Stopping background process SMCO
Shutting down instance: further logons disabled
Stopping background process QMNC
Stopping background process MMNL
Stopping background process MMON
License high water mark = 24
All dispatchers and shared servers shutdown
Wed Aug 03 15:03:36 2016
Non critical error ORA-48913 caught while writing to trace file "/oracle/diag/rdbms/tedw_dev/SID/trace/SID_ora_21399.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [5242880] reached
Writing to the above trace file is disabled for now on...
Wed Aug 03 15:14:30 2016
License high water mark = 24
USER (ospid: 24905): terminating the instance
Instance terminated by USER, pid = 24905
Wed Aug 03 15:15:25 2016
Adjusting the default value of parameter parallel_max_servers
from 640 to 370 due to the value of parameter processes (400)
Starting ORACLE instance (restrict)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 16
Number of processor cores in the system is 8
Number of processor sockets in the system is 4
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =68
LICENSE_MAX_USERS = 0
SYS auditing is enabled
Re: Database Hangs for Cold Backup [message #654487 is a reply to message #654486] Wed, 03 August 2016 15:23 Go to previous message
BlackSwan
Messages: 25745
Registered: January 2009
Location: SoCal
Senior Member
48913, 00000, "Writing into trace file failed, file size limit [%s] reached"
// *Cause:An attempt was made to write into a trace file that exceeds 
//        the trace's file size limit
// *Action:increase the trace's file size limit.

>Non critical error ORA-48913 caught while writing to trace file "/oracle/diag/rdbms/tedw_dev/SID/trace/SID_ora_21399.trc"
>Error message: ORA-48913: Writing into trace file failed, file size limit [5242880] reached

what clues exist within trace file above?

>Adjusting the default value of parameter parallel_max_servers
>from 640 to 370 due to the value of parameter processes (400)
Why is PARALLEL_MAX_SERVERS set ridiculously high?

>Starting ORACLE instance (restrict)
why is DB starting (restrict)?
Previous Topic: BD Console is not runnin
Next Topic: having trouble in opening enterprise manger
Goto Forum:
  


Current Time: Wed Dec 13 06:46:08 CST 2017

Total time taken to generate the page: 0.02190 seconds