RMAN-02005: token too big
- 2 Answers
- 7264 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / guest
Cause: A token longer than 1000 bytes was encountered
Action: Tokens must be separated by whitespace or
punctuation. Either add the missing whitespace or
punctuation, or shorten the token.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / ak
Do a little thing when this error comes. In my case i was started RMAN after the instance was started, means at idle instance i was attemp to start RMAN, but actually RMAN Has to start after the STARTUP of target database without catalog.
So after the start the DATABASE then hit the command
RMAN TARGET / NOCATALOG
and here we go. error is gone..!
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-25531: MTTR specified is too small: string
AMD-00129: dimension #string: RDBMS GID column not specified
RMAN-06085: must use SET NEWNAME command to restore datafile string
ORA-08341: On nCUBE, this command can only be executed from instance 1.
RMAN-06441: cannot upgrade catalog - catalog is already newer than this RMAN
DRG-10827: open_con must be performed before count_last
ORA-01674: data file string is an old incarnation rather than current file
ORA-26505: unexpected internal null
NNL-00856: Average rename processing time: string
ORA-36686: (XSDPART24) Value number is not in partition number.
ORA-00470: LGWR process terminated with error
ORA-26006: Incorrect bind variable in column string's sql expression - string
Oracle Errors 
