Re: Question: RMAN - Getting closer...

That makes sense.

This is SO maddening, though.

My 'revised' command is:

run {allocate channel dev2 type disk; allocate auxiliary channel dev1 type disk;sql "alter session set nls_date_format=''MM-DD-YYYY HH24:MI:SS''"; recover tablespace small_tables_2 until time "to_date('09-01-2005 09:45:01','MM-DD-YYYY HH24:MI:SS')";}

and now the error message is:

RMAN-06136: ORACLE error from auxiliary database: ORA-01858: a non-numeric character was found where a numeric was expected RMAN-06097: text of failing SQL statement: select to_date('SEP 01 2005 09:45:01') from sys.dual
RMAN-06099: error occurred in source file: krmk.pc, line: 4392

What is very curious is that if I enter the same command string again, I get that unidentified '2122' error.

So where the heck is it getting 'SEP 01 2005 09:45:01' from??? I'm now at a similar state I was in before the kind poster pointed out bug 1516488 in 8i; the error message is not quite the same, but I'm still getting a date format that's wrong, and I can't see from where...

I set the nls_date_format in the init file of the db, the OS environment, fired in a sql statement before running the recover/restore string, and included the format clause in the recover/restore string.

To be clear: the way I'm setting the environment variable is: nls_date_format='MM-DD-YYYY HH24:MI:SS'; export nls_date_format

I appreciate people's patience, but GEEZ this is a PITA. ;) Received on Fri Sep 02 2005 - 11:17:34 CDT