Analysing Alertlog entries

Question

Hi all,
I am getting a few errors/entries in alertlog which I am not able to understand, need your help.
I am on 10.1.0.2 64 bit Enterprise Edition, IBM/AIX RISC System/6000
Backup is scheduled at 05.05 / 13.15 / 21.15  via crontab, not sure what does below entry mean...
ya background process DM00,  DW01 & DW02 have started to execute, is there anything more that can be analyzed?
1)
Thu Jan 30 05:05:08 2014
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=40, OS id=999536
         to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_31', 'SYSTEM');
kupprdp: worker process DW01 started with worker id=1, pid=41, OS id=839788
         to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_31', 'SYSTEM');
kupprdp: worker process DW02 started with worker id=2, pid=44, OS id=651502
         to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_31', 'SYSTEM');
Thu Jan 30 05:39:34 2014
Private_strands 16 at log switch
The backup ends in about 1.5hrs but post 5 hours i get below entries.
2)
Thu Jan 30 10:32:40 2014
SMON offlining US=12
Freeing IMU pool for usn 12
SMON offlining US=13
Freeing IMU pool for usn 13
SMON offlining US=14
Freeing IMU pool for usn 14
SMON offlining US=15
Freeing IMU pool for usn 15
SMON offlining US=16
Freeing IMU pool for usn 16
SMON offlining US=17
Freeing IMU pool for usn 17
SMON offlining US=18
Freeing IMU pool for usn 18
SMON offlining US=19
Freeing IMU pool for usn 19
SMON offlining US=20
Freeing IMU pool for usn 20
SMON offlining US=21
Freeing IMU pool for usn 21
SMON offlining US=22
Freeing IMU pool for usn 22
Thu Jan 30 10:56:51 2014
I am confused as to why it says SMON offlining.... its a PROD database & is running fine... should i check the most resent trace files (as there is no entry "check xyz.trc for errors")to check this or this is normal?
Both 1) & 2) repeat (while start of backup(DM,DW start) & a few mins later (offlining) backup time)
1 thing to mention, due to insufficient space on backup path, backup was not successfull, hence i had to run backup script manually, backup succeeded, in alert log I have the 1) issue & NOT THE 2) issue ie; offlining SMON.
Please explain me on this...
3)
Also I get ORA-00600... is this due to space issue? coz as i checked for "IBM AIX RISC System/6000 Error: 5: I/O error" error it said space issue, so after i cleared a few GB the backup was a success. I am aware that if we get ORA-00600 we need to contact Oracle Support, but here should contact/not not sure as I get ORA-600 only when backup fails due to insufficient space...
Wed Jan 29 14:47:44 2014
Errors in file /home/oracle/bdump/oracle_dw01_1175588.trc:
ORA-27045: unable to close the file
IBM AIX RISC System/6000 Error: 5: I/O error
Additional information: 3
ORA-19502: write error on file "/user1/dlybkp/dp_bkp/dp_29Jan141315.dmp", blockno 1485877 (blocksize=4096)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 5: I/O error
Additional information: -1
Additional information: 262144
Wed Jan 29 14:47:44 2014
Errors in file /home/oracle/bdump/oracle_dw01_1175588.trc:
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], []
Wed Jan 29 14:49:45 2014
Private_strands 16 at log switch
Errors in file /home/oracle/bdump/oracle_dw02_991274.trc:
ORA-27045: unable to close the file
IBM AIX RISC System/6000 Error: 5: I/O error
Additional information: 3
ORA-19502: write error on file "/user1/dlybkp/dp_bkp/dp_23Jan141315.dmp", blockno 1650786 (blocksize=4096)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 5: I/O error
Additional information: -1
Additional information: 262144
Thu Jan 23 14:29:44 2014
Errors in file /home/oracle/bdump/oracle_dw02_991274.trc:
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], []
Thu Jan 23 14:31:58 2014
4)
Wed Jan 29 01:43:23 2014
WARNING: db_create_file_dest is same as db_recovery_file_dest
Wed Jan 29 02:59:17 2014
Private_strands 16 at log switch
Thread 1 advanced to log sequence 23212
dont know why this came as i never even checked for "show parameter db_recovery"...
yes its just a warning, can be ignored...but any specific reason why this warning has appeared?
Please let me know if I have missed any information to post.
Thanks,
Mohib

Answer 1

Thanks all,
1) The solution is Doc ID 455021.1 (i.e. Ignore these informational messages as it is safe. This problem is handled in bug 6347775 base bug 4892288 (not published externally, fixed in version 11.2)).
2) As mentioned by Alvaro, Regarding SMON offlining undo segments: Yes it's not a problem. In AUM smon automatically onlines and offlines undo segments as per database demand. Export uses read consistency mechanism (undo) to export the data in a consistent manner at the SCN where the export started. That's why you see SMON cleaning up and freeing undo segments after it's done running.
(Doc ID 396863.1,
When are UNDO segments OFFLINED?
Answer:
SMON decides on the # of undo segs to offline and drop based on the max transaction concurrency over a 12 hour period in 9i.  This behavior is altered in 10g where the max concurrency is maintained over a 7-day period.  Moreover, in 10g SMON doesn't drop the extra undo segs, but simply offlines them.
SMON uses the same values with "fast ramp up" to adjust the number of undo segments online.
Doc ID 1495163.1
SMON performs many database maintenance tasks, including:
Maintains the undo tablespace by onlining, offlining, and shrinking the undo segments based on undo space usage statistics)
3) As mentioned by Mark D Powell, one shall refer to Doc ID 29616.1 i.e. need to upgrade from 10.1 to 10.2.
4) WARNING: db_create_file_dest is same as db_recovery_file_dest in alertlog, As mentioned by Alvaro, There is a bug which affects 10.1 release and it is fixed on 10.2 i.e. should upgrade to 10.2 release.
Kindly correct me if I am wrong anywhere.
Thanks All once again for support
Mohib