cancel
Showing results for 
Search instead for 
Did you mean: 

rman-00600

aa2
Level 2

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?

9 REPLIES 9

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
All of those are Oracle errors.
Maybe ask on an Oracle forum?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Google found this:
http://oracle-dba-quickanswers.blogspot.co.za/2011/10/rman-00600-internal-error-arguments.html?m=1

Solution:


3 Bug.3443934 (11) ATTN/CTL-C FROM RMAN> CAUSES LOOP:
3 Bug.6781746 (33) RMAN-600[2012] WHEN SWAP AND BACKUP SPACE ARE EXHAUSTED CAUSES LOOP:
3 Bug.6735007 (31) RMAN-00600[2012]:
3 Bug.5015641 (33) RMAN-1006, RMAN-600 [2012] AND BIGGER RMAN LOGFILE WHEN FS OF $OH IS FULL:

Tousif
Level 6

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,

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@aa2

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"

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

 

 

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Everything that I have seen indicates a problem at OS level. Swap space or file system.
NBU is MML. If it has worked fine up to now, ask yourself what has changed?

If nothing has changed at NBU level, how can the issue be with NBU?

You can try to log a support call with Veritas, but they will proprobably tell you that your NBU version is no longer supported. Support ended 7 months ago.

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?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
No. NetBackup has not shut down. There are newer, supported levels. 7.7.x and 8.0.

You can create log folders to trace NBU.
dbclient on Oracle client (777 permissions), bpbrm and bptm on the media server, bprd on the master (restart NBU after creating the folder).

Logging should be at least at level 3.
My guess is that dbclient will contain most info as that is the direct interface with Oracle.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Thanks for changing 'shut down' to EOS.