I got this error while trying to perform an import from another 19c database but apparently with a higher TZ version: The solution is to perform the TZ upgrade of the database. Check the current time zone version: Let’s see what’s the latest time zone to which we can upgrade to: We can see that…
While cloning a schema within the same database, I encountered the following exception: While I was interested in importing only table data, I have created the following PARFILE: And the execution was looking like this: This is happening due to the fact that when executing the import, the impdp is trying to create those objects…
This is how you can see it: RMAN SQL>alter session set nls_date_format=’dd/mm/yy hh24:mi:ss’; SQL>select sid, totalwork, sofar,(sofar/totalwork) * 100 per_done,start_time, sysdate + time_remaining/3600/24 end_at from v$session_longops where totalwork > sofar and lower(opname) not like ‘%aggregate%’ and lower(opname) like ‘rman%’; SID START_TIME TOTALWORK SOFAR PER_DONE END_AT —– —————– ———- ———- ———- —————– —————– 491 18/08/10 20:13:45…
Recently I had to make a clone of a schema and to move it from production to development using a different name at destination. First grab all the information you need: select username,default_tablespace from dba_users where username like ‘&USERNAME’; # Now get the tablespace name from the previous statement and get the datafiles below: select…
