Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-02005: token too big
- 2 Answers
- 8571 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 |
PCC-00105: Keyword WORK required here by ANSI
RMAN-08041: partial resync skipped, controlfile is not current or backup
ORA-01571: redo version string incompatible with ORACLE version string
ORA-12520: TNS:listener could not find available handler for requested type of server
ORA-22346: Type has cyclical dependency. Should use CASCADE option
IMP-00033: Warning: Table "string" not found in export file
ORA-01025: UPI parameter out of range
EXP-00103: The FLASHBACK_TIME parameter was invalid
ORA-28601: invalid [no]MINIMIZE option
ORA-08103: object no longer exists
ORA-39146: schema "string" does not exist
ORA-02822: Invalid block offset
Oracle Errors 
