08-30-2017 09:49 PM - edited 08-31-2017 10:43 PM
Hello, I have an error about rman backup.
DB Server : AIX 5.3 oracle 9i netbackup 7.5.0.6
Backup master server:centos 6.8 netbackup 7.5.0.6
A good backup suddenly produces the following error:
===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01006: error signalled during parse
RMAN-00600: internal error, arguments [2012] [] [] [] []
The above message will continue to be generated until the filesystem is full.
What is the solution?
08-30-2017 10:08 PM
08-30-2017 10:13 PM
08-31-2017 02:37 AM
Hello,
Kindly confirm with your DBA about any changes done recenlty in backup script, Filesystem utilizatiion and in database configuration .
Error:
===========================================================
RMAN-00558: error encountered while parsing input commands <- Input command have syntax error
RMAN-01006: error signalled during parse
RMAN-00600: internal error, arguments [2012] [] [] [] [] <- Filesystem is full.
Reference:
https://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmcnctg.htm#BRADV005
https://setaoffice.com/2012/04/24/oracle-rman-error-rman-00600-internal-error-arguments-2012/
Regards,
08-31-2017 03:09 AM
As you can see, the error is actually because of swap and/or filesystem running out of space.
It is therefore the other way round, not "... continue to be generated until the filesystem is full"
08-31-2017 05:14 PM
Hi Marianne
First of all thank you for your quick reply.
I have already confirmed the Oracle bug you mentioned.
But there is no solution.
Our dba contacted Oracle Support Center
bug 9072227: rman restore hangs getting rman-00600 [2012] error
It seems to be a problem similar to the bug, and I have been asked to reconfigure the MML or ask the MML vendor to confirm it.
"The MML vendor will generally perform additional diagnostics through the SBT (MML) level trace, and the vendor company will provide the measures according to the analysis result."
How do you trace SBT level?
Thanks
08-31-2017 11:02 PM
08-31-2017 11:40 PM - edited 08-31-2017 11:42 PM
I know that Netbackup has been EOS
So that's more of a problem.
Anyway, the problem has to be solved, but more and more customers are continuing to have problems. The same problem is happening in 10 places today.
Is there a way to set the trace at MML level?
08-31-2017 11:47 PM
09-01-2017 08:59 AM