Remap schema
Hi,
There are two users in my database
INFAI2X_RO
INFAI2
There are objects and views which are owned by INFAI2X_RO and the base tables are owned by INFAI2.
How can I compile the views and synonyms such that they become valid?
Regards,
VN
Hello;
I believe this will work :
SET heading off;
SET feedback off;
SET echo off;
SET lines 999;
SPOOL invalid.sql
SELECT 'ALTER ' || object_type || ' ' || owner || '.' || object_name
|| ' COMPILE;'
FROM dba_objects
WHERE status = 'INVALID'
AND owner in ('INFAI2X_RO')
AND object_type IN ('VIEW');
SPOOL off;
SET heading on;
SET feedback on;
SET echo on;
@invalid.sqlYou don't have to do anything to synonyms. When you touch them they become valid.
Best Regards
mseberg
Similar Messages
-
HI
oracle version 10g r2
I use datapump export to export Metadat only for 3 schemas (IGL,TEXXON,OLI)
this export is done by user --- IGL
I Try to import(iimpdp) this 3 schemas in other database same oracle version using the follwoing command
impdp system@twmin DIRECTORY=DBPUMPDIR DUMPFILE=twmin_schema_0120090109.dmp,twmin_schema_0220090109.dmp SCHEMAS=IGL,TEXXON,OLI
i hit lot of ORA Errors , the main ORA Errors is
ORA-01435: user does not exist
ORA-31625: error changing username from SYSTEM to IGL
AND I USE REMAP SCHEMA OPTION
impdp system@twmin DIRECTORY=DBPUMPDIR REMAP_SCHEMA=IGL:IGLTEST DUMPFILE=twmin_schema_0120090109.dmp,twmin_schema_0220090109.dmp
This option also through lot of ora error , because it says other user lik -- OLI
ORA-31625: error changing username from SYSTEM to OLI
ORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"IGLTEST"."SYS_EXPORT_SCHEMA_02" creation failed
ORA-31625: error changing username from SYSTEM to TEXXON
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 4715
ORA-01435: user does not exist
and it will import the procedure,packages from IGL to IGLTEST but it did'nt
create the table structure
how i can import this 3 schema to other database without error
rdsHi..
ORA-31625: error changing username from SYSTEM to OLIORA-39112: Dependent object type COMMENT skipped, base object type TABLE:"IGLTEST"."SYS_EXPORT_SCHEMA_02" creation failed
ORA-31625: error changing username from SYSTEM to TEXXON
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 4715
ORA-01435: user does not exist>
Last line reads ORA-01435: user does not exist. First create the user IGLTEST and then import the data.
HTH
Anand -
Datapump: cloning schema, target has multiple size. How to solve?
Hi all,
I am quite unfamiliar with dataump - i've used imp / exp before.
Now I need to clone a schema and have to remap the tablespaces. The forum advised me to use datapump but now I have some problems with it:
source schema name: DEV_6
target schema name: TESTUSER
I checked the size of the schemas with the following statement:
select owner, sum(bytes)/1024/1024 tsize
from dba_segments
group by owner
order by tsize desc;
My source (DEV_6) has the size of 4GB.
After importing the target (TESTUSER) has a size of more than 32GB (import is still running)
I exported the schema with following statement:
expdp DIRECTORY=DATA_PUMP_DIR DUMPFILE=DEV_6.expdp LOGFILE=DEV_6_exp.log SCHEMAS=DEV_6
For importing and remapping schema and tablespace I used the following statement:
impdp LOGFILE=TESTUSER_imp.log REMAP_TABLESPACE='AMES_DEV_PERM':'TESTUSER_PERM','DEV_TRUNK_DATA_XXL':'TESTUSER_PERM' REMAP_SCHEMA='DEV_6':'TESTUSER' SCHEMAS='DEV_6' DIRECTORY=DATA_PUMP_DIR DUMPFILE=DEV_6.expdp
We are using 11.2.0.1.
Any ideas how to solve this problem?
Thanks in advance,
Andreas
Edited by: Andreas S. on 07.09.2012 03:21Hi,
I think I found the problem:
The definition of the tablespaces differs:
TABLESPACE_NAME BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_SIZE ALLOCATION_TYPE
TABLESPACE_ORG 8192 65536 null 1 null SYSTEM
TABLESPACE_NEW 8192 131072000 131072000 1 2147483645 SYSTEM
Andreas -
Data Pump - expdp and slow performance on specific tables
Hi there
I have af data pump export af a schema. Most of the 700 tables is exported very quickly (direct path) but a couple of them seems to be extremenly slow.
I have chekced:
- no lobs
- no long/raw
- no VPD
- no partitions
- no bitmapped index
- just date, number, varchar2's
I'm runing with trace 400300
But I'm having trouble reading the output from it. It seems that some of the slow performning tables is runinng with method 4??? Can anyone find an explanation for the method in the trace:
1 > direct path (i think)
2 > external table (i think)
4 > ?
others?
I have done some stats using v$filestat/v$session_wait (history) - and it seems that we always wait for DB seq file read - and doing lots and lots of SINGLEBLKRDS. Not undo is read
I have a table 2.5 GB -> 3 minutes
and then this (in my eyes) similar table 2.4 GB > 1½ hrs.
There are 367.000 blks (8 K) and avg rowlen = 71
I'm on Oracle 11.2 on a Linux box with plenty of RAM and CPU power.
Trace file /opt/oracle112/diag/rdbms/prod/prod/trace/prod_dw00_24268.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /opt/oracle112/product/11.2.0.2/dbhome_1
System name: Linux
Node name: tiaprod.thi.somethingamt.dk
Release: 2.6.18-194.el5
Version: #1 SMP Mon Mar 29 22:10:29 EDT 2010
Machine: x86_64
VM name: Xen Version: 3.4 (HVM)
Instance name: prod
Redo thread mounted by this instance: 1
Oracle process number: 222
Unix process pid: 24268, image: [email protected] (DW00)
*** 2011-09-20 09:39:39.671
*** SESSION ID:(401.8395) 2011-09-20 09:39:39.671
*** CLIENT ID:() 2011-09-20 09:39:39.671
*** SERVICE NAME:(SYS$BACKGROUND) 2011-09-20 09:39:39.671
*** MODULE NAME:() 2011-09-20 09:39:39.671
*** ACTION NAME:() 2011-09-20 09:39:39.671
KUPP:09:39:39.670: Current trace/debug flags: 00400300 = 4195072
*** MODULE NAME:(Data Pump Worker) 2011-09-20 09:39:39.672
*** ACTION NAME:(SYS_EXPORT_SCHEMA_09) 2011-09-20 09:39:39.672
KUPW:09:39:39.672: 0: ALTER SESSION ENABLE PARALLEL DML called.
KUPW:09:39:39.672: 0: ALTER SESSION ENABLE PARALLEL DML returned.
KUPC:09:39:39.693: Setting remote flag for this process to FALSE
prvtaqis - Enter
prvtaqis subtab_name upd
prvtaqis sys table upd
KUPW:09:39:39.819: 0: KUPP$PROC.WHATS_MY_ID called.
KUPW:09:39:39.819: 1: KUPP$PROC.WHATS_MY_ID returned.
KUPW:09:39:39.820: 1: worker max message number: 1000
KUPW:09:39:39.822: 1: Full cluster access allowed
KUPW:09:39:39.823: 1: Original job start time: 11-SEP-20 09:39:38 AM
KUPW:09:39:39.862: 1: KUPP$PROC.WHATS_MY_NAME called.
KUPW:09:39:39.862: 1: KUPP$PROC.WHATS_MY_NAME returned. Process name: DW00
KUPW:09:39:39.862: 1: KUPV$FT_INT.GET_INSTANCE_ID called.
KUPW:09:39:39.866: 1: KUPV$FT_INT.GET_INSTANCE_ID returned. Instance name: prod
KUPW:09:39:39.870: 1: ALTER SESSION ENABLE RESUMABLE called.
KUPW:09:39:39.870: 1: ALTER SESSION ENABLE RESUMABLE returned.
KUPW:09:39:39.871: 1: KUPF$FILE.INIT called.
KUPW:09:39:39.996: 1: KUPF$FILE.INIT returned.
KUPW:09:39:39.998: 1: KUPF$FILE.GET_MAX_CSWIDTH called.
KUPW:09:39:39.998: 1: KUPF$FILE.GET_MAX_CSWIDTH returned.
KUPW:09:39:39.998: 1: Max character width: 1
KUPW:09:39:39.998: 1: Max clob fetch: 32757
KUPW:09:39:39.998: 1: Max varchar2a size: 32757
KUPW:09:39:39.998: 1: Max varchar2 size: 7990
KUPW:09:39:39.998: 1: In procedure GET_PARAMETERS
KUPW:09:39:40.000: 1: In procedure GET_METADATA_FILTERS
KUPW:09:39:40.001: 1: In procedure GET_METADATA_TRANSFORMS
KUPW:09:39:40.002: 1: In procedure GET_DATA_FILTERS
KUPW:09:39:40.004: 1: In procedure GET_DATA_REMAPS
KUPW:09:39:40.005: 1: In procedure PRINT_MT_PARAMS
KUPW:09:39:40.005: 1: Master table : "SYSTEM"."SYS_EXPORT_SCHEMA_09"
KUPW:09:39:40.005: 1: Metadata job mode : SCHEMA_EXPORT
KUPW:09:39:40.005: 1: Debug enable : TRUE
KUPW:09:39:40.005: 1: Profile enable : FALSE
KUPW:09:39:40.005: 1: Transportable enable : FALSE
KUPW:09:39:40.005: 1: Metrics enable : FALSE
KUPW:09:39:40.005: 1: db version : 11.2.0.2.0
KUPW:09:39:40.005: 1: job version : 11.2.0.0.0
KUPW:09:39:40.005: 1: service name :
KUPW:09:39:40.005: 1: Current Edition : ORA$BASE
KUPW:09:39:40.005: 1: Job Edition :
KUPW:09:39:40.005: 1: Abort Step : 0
KUPW:09:39:40.005: 1: Access Method : AUTOMATIC
KUPW:09:39:40.005: 1: Data Options : 0
KUPW:09:39:40.006: 1: Dumper directory :
KUPW:09:39:40.006: 1: Master only : FALSE
KUPW:09:39:40.006: 1: Data Only : FALSE
KUPW:09:39:40.006: 1: Metadata Only : FALSE
KUPW:09:39:40.006: 1: Estimate : BLOCKS
KUPW:09:39:40.006: 1: Data error logging table :
KUPW:09:39:40.006: 1: Remote Link :
KUPW:09:39:40.006: 1: Dumpfile present : TRUE
KUPW:09:39:40.006: 1: Table Exists Action :
KUPW:09:39:40.006: 1: Partition Options : NONE
KUPW:09:39:40.006: 1: Tablespace Datafile Count: 0
KUPW:09:39:40.006: 1: Metadata Filter Index : 1 Count : 10
KUPW:09:39:40.006: 1: 1 Name - INCLUDE_USER
KUPW:09:39:40.006: 1: Value - TRUE
KUPW:09:39:40.006: 1: Object Name - SCHEMA_EXPORT
KUPW:09:39:40.006: 1: 2 Name - SCHEMA_EXPR
KUPW:09:39:40.006: 1: Value - IN ('TIA')
KUPW:09:39:40.006: 1: 3 Name - NAME_EXPR
KUPW:09:39:40.006: 1: Value - ='ACC_PAYMENT_SPECIFICATION'
KUPW:09:39:40.006: 1: Object - TABLE
KUPW:09:39:40.006: 1: 4 Name - INCLUDE_PATH_EXPR
KUPW:09:39:40.006: 1: Value - IN ('TABLE')
KUPW:09:39:40.006: 1: 5 Name - ORDERED
KUPW:09:39:40.006: 1: Value - FALSE
KUPW:09:39:40.006: 1: Object - TABLE_DATA
KUPW:09:39:40.006: 1: 6 Name - NO_XML
KUPW:09:39:40.006: 1: Value - TRUE
KUPW:09:39:40.006: 1: Object - XMLSCHEMA/EXP_XMLSCHEMA
KUPW:09:39:40.006: 1: 7 Name - XML_OUTOFLINE
KUPW:09:39:40.006: 1: Value - FALSE
KUPW:09:39:40.006: 1: Object - TABLE/TABLE_DATA
KUPW:09:39:40.006: 1: 8 Name - XDB_GENERATED
KUPW:09:39:40.006: 1: Value - FALSE
KUPW:09:39:40.006: 1: Object - TABLE/TRIGGER
KUPW:09:39:40.007: 1: 9 Name - XDB_GENERATED
KUPW:09:39:40.007: 1: Value - FALSE
KUPW:09:39:40.007: 1: Object - TABLE/RLS_POLICY
KUPW:09:39:40.007: 1: 10 Name - PRIVILEGED_USER
KUPW:09:39:40.007: 1: Value - TRUE
KUPW:09:39:40.007: 1: MD remap schema Index : 4 Count : 0
KUPW:09:39:40.007: 1: MD remap other Index : 5 Count : 0
KUPW:09:39:40.007: 1: MD Transform ddl Index : 2 Count : 11
KUPW:09:39:40.007: 1: 1 Name - DBA
KUPW:09:39:40.007: 1: Value - TRUE
KUPW:09:39:40.007: 1: Object - JOB
KUPW:09:39:40.007: 1: 2 Name - EXPORT
KUPW:09:39:40.007: 1: Value - TRUE
KUPW:09:39:40.007: 1: 3 Name - PRETTY
KUPW:09:39:40.007: 1: Value - FALSE
KUPW:09:39:40.007: 1: 4 Name - SQLTERMINATOR
KUPW:09:39:40.007: 1: Value - FALSE
KUPW:09:39:40.007: 1: 5 Name - CONSTRAINTS
KUPW:09:39:40.007: 1: Value - FALSE
KUPW:09:39:40.007: 1: Object - TABLE
KUPW:09:39:40.007: 1: 6 Name - REF_CONSTRAINTS
KUPW:09:39:40.007: 1: Value - FALSE
KUPW:09:39:40.007: 1: Object - TABLE
KUPW:09:39:40.007: 1: 7 Name - OID
KUPW:09:39:40.007: 1: Value - TRUE
KUPW:09:39:40.007: 1: Object - TABLE
KUPW:09:39:40.007: 1: 8 Name - RESET_PARALLEL
KUPW:09:39:40.007: 1: Value - TRUE
KUPW:09:39:40.007: 1: Object - INDEX
KUPW:09:39:40.007: 1: 9 Name - OID
KUPW:09:39:40.007: 1: Value - TRUE
KUPW:09:39:40.007: 1: Object - TYPE
KUPW:09:39:40.007: 1: 10 Name - OID
KUPW:09:39:40.007: 1: Value - TRUE
KUPW:09:39:40.007: 1: Object - INC_TYPE
KUPW:09:39:40.007: 1: 11 Name - REVOKE_FROM
KUPW:09:39:40.008: 1: Value - SYSTEM
KUPW:09:39:40.008: 1: Object - ROLE
KUPW:09:39:40.008: 1: Data Filter Index : 6 Count : 0
KUPW:09:39:40.008: 1: Data Remap Index : 7 Count : 0
KUPW:09:39:40.008: 1: MD remap name Index : 8 Count : 0
KUPW:09:39:40.008: 1: In procedure DISPATCH_WORK_ITEMS
KUPW:09:39:40.009: 1: In procedure SEND_MSG. Fatal=0
KUPW:09:39:40.009: 1: KUPC$QUEUE.TRANSCEIVE called.
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
kwqberlst rqan->lascn_kwqiia > 0 block
kwqberlst rqan->lascn_kwqiia 7
kwqberlst ascn -90145310 lascn 22
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
KUPW:09:39:40.036: 1: KUPC$QUEUE.TRANSCEIVE returned. Received 2011
KUPW:09:39:40.036: 1: DBMS_LOB.CREATETEMPORARY called.
KUPW:09:39:40.037: 1: DBMS_LOB.CREATETEMPORARY returned.
KUPW:09:39:40.038: 1: Flags: 18
KUPW:09:39:40.038: 1: Start sequence number:
KUPW:09:39:40.038: 1: End sequence number:
KUPW:09:39:40.038: 1: Metadata Parallel: 1
KUPW:09:39:40.038: 1: Primary worker id: 1
KUPW:09:39:40.041: 1: In procedure GET_TABLE_DATA_OBJECTS
KUPW:09:39:40.041: 1: In procedure CREATE_MSG
KUPW:09:39:40.041: 1: KUPV$FT.MESSAGE_TEXT called.
KUPW:09:39:40.041: 1: KUPV$FT.MESSAGE_TEXT returned.
KUPW:09:39:40.041: 1: In procedure SEND_MSG. Fatal=0
KUPW:09:39:40.041: 1: KUPC$QUEUE_INT.SEND called.
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
kwqberlst rqan->lascn_kwqiia > 0 block
kwqberlst rqan->lascn_kwqiia 7
kwqberlst ascn -90145310 lascn 22
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
KUPW:09:39:40.044: 1: KUPC$QUEUE_INT.SEND returned.
KUPW:09:39:40.044: 1: Estimate in progress using BLOCKS method...
KUPW:09:39:40.044: 1: In procedure UPDATE_TYPE_COMPLETION_ROW
KUPW:09:39:40.044: 1: Old Seqno: 0 New Path: SCHEMA_EXPORT/TABLE/TABLE_DATA PO Num: -5 New Seqno: 62
KUPW:09:39:40.046: 1: Created type completion for duplicate 62
KUPW:09:39:40.046: 1: In procedure CREATE_MSG
KUPW:09:39:40.046: 1: KUPV$FT.MESSAGE_TEXT called.
KUPW:09:39:40.046: 1: KUPV$FT.MESSAGE_TEXT returned.
KUPW:09:39:40.046: 1: In procedure SEND_MSG. Fatal=0
KUPW:09:39:40.046: 1: KUPC$QUEUE_INT.SEND called.
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
kwqberlst rqan->lascn_kwqiia > 0 block
kwqberlst rqan->lascn_kwqiia 7
kwqberlst ascn -90145310 lascn 22
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
KUPW:09:39:40.047: 1: KUPC$QUEUE_INT.SEND returned.
KUPW:09:39:40.047: 1: Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
KUPW:09:39:40.048: 1: In procedure CONFIGURE_METADATA_UNLOAD
KUPW:09:39:40.048: 1: Phase: ESTIMATE_PHASE Filter Name: Filter Value:
KUPW:09:39:40.048: 1: DBMS_METADATA.OPEN11.2.0.0.0 called.
KUPW:09:39:40.182: 1: DBMS_METADATA.OPEN11.2.0.0.0 returned. Source handle: 100001
KUPW:09:39:40.182: 1: DBMS_METADATA.SET_FILTER called. metadata_phase: ESTIMATE_PHASE
KUPW:09:39:40.182: 1: DBMS_METADATA.SET_FILTER returned. In function GET_NOEXP_TABLE
KUPW:09:39:40.194: 1: DBMS_METADATA.SET_PARSE_ITEM called.
*** 2011-09-20 09:39:40.325
KUPW:09:39:40.325: 1: DBMS_METADATA.SET_PARSE_ITEM returned.
KUPW:09:39:40.325: 1: DBMS_METADATA.SET_COUNT called.
KUPW:09:39:40.328: 1: DBMS_METADATA.SET_COUNT returned.
KUPW:09:39:40.328: 1: DBMS_METADATA.FETCH_XML_CLOB called.
*** 2011-09-20 09:39:42.603
KUPW:09:39:42.603: 1: DBMS_METADATA.FETCH_XML_CLOB returned.
KUPW:09:39:42.603: 1: In procedure CREATE_TABLE_DATA_OBJECT_ROWS
KUPW:09:39:42.603: 1: In function GATHER_PARSE_ITEMS
KUPW:09:39:42.603: 1: In function CHECK_FOR_REMAP_NETWORK
KUPW:09:39:42.603: 1: Nothing to remap
KUPW:09:39:42.603: 1: In procedure BUILD_OBJECT_STRINGS
KUPW:09:39:42.604: 1: In procedure LOCATE_DATA_FILTERS
KUPW:09:39:42.604: 1: In function NEXT_PO_NUMBER
KUPW:09:39:42.620: 1: In procedure DETERMINE_METHOD_PARALLEL
KUPW:09:39:42.620: 1: flags mask: 0
KUPW:09:39:42.620: 1: dapi_possible_meth: 1
KUPW:09:39:42.620: 1: data_size: 3019898880
KUPW:09:39:42.620: 1: et_parallel: TRUE
KUPW:09:39:42.620: 1: object: TABLE_DATA:"TIA"."ACC_PAYMENT_SPECIFICATION" <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
KUPW:09:39:42.648: 1: l_dapi_bit_mask: 7
KUPW:09:39:42.648: 1: l_client_bit_mask: 7
KUPW:09:39:42.648: 1: TABLE_DATA:"TIA"."ACC_PAYMENT_SPECIFICATION" either, parallel: 12 <<<<< Here is says either (I thought that was method ?) <<<<<<<<<<<<<<<<
KUPW:09:39:42.648: 1: FORALL BULK INSERT called.
KUPW:09:39:42.658: 1: FORALL BULK INSERT returned.
KUPW:09:39:42.660: 1: DBMS_LOB.TRIM called. v_md_xml_clob
KUPW:09:39:42.660: 1: DBMS_LOB.TRIM returned.
KUPW:09:39:42.660: 1: DBMS_METADATA.FETCH_XML_CLOB called.
KUPW:09:39:42.678: 1: DBMS_METADATA.FETCH_XML_CLOB returned.
KUPW:09:39:42.678: 1: DBMS_LOB.CREATETEMPORARY called.
KUPW:09:39:42.678: 1: DBMS_LOB.CREATETEMPORARY returned.
KUPW:09:39:42.678: 1: In procedure UPDATE_TD_ROW_EXP with seqno: 62
KUPW:09:39:42.680: 1: 1 rows fetched
KUPW:09:39:42.680: 1: In function NEXT_PO_NUMBER
KUPW:09:39:42.680: 1: Next table data array entry: 1 Parallel: 12 Size: 3019898880 Method: 4Creation_level: 0 <<<<<<<<<<<<<<<< HERE IT SAYS METHOD = 4 and PARALLEL=12 (I'm not using the parallel parameter ???) <<<<<<<<<<<<<<<<<<
KUPW:09:39:42.681: 1: In procedure UPDATE_TD_BASE_PO_INFO
KUPW:09:39:42.683: 1: Updated 1 td objects with bpo between 1 and 1
KUPW:09:39:42.684: 1: Send table_data_varray called. Count: 1
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
kwqberlst rqan->lascn_kwqiia > 0 block
kwqberlst rqan->lascn_kwqiia 7
kwqberlst ascn -90145310 lascn 22
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
KUPW:09:39:42.695: 1: Send table_data_varray returned.
KUPW:09:39:42.695: 1: In procedure SEND_MSG. Fatal=0
KUPW:09:39:42.695: 1: In procedure UPDATE_TYPE_COMPLETION_ROW
KUPW:09:39:42.695: 1: Old Seqno: 62 New Path: PO Num: -5 New Seqno: 0
KUPW:09:39:42.695: 1: Object count: 1
KUPW:09:39:42.697: 1: 1 completed for 62
KUPW:09:39:42.697: 1: DBMS_METADATA.CLOSE called. Handle: 100001
KUPW:09:39:42.697: 1: DBMS_METADATA.CLOSE returned.
KUPW:09:39:42.697: 1: In procedure CREATE_MSG
KUPW:09:39:42.697: 1: KUPV$FT.MESSAGE_TEXT called.
KUPW:09:39:42.698: 1: KUPV$FT.MESSAGE_TEXT returned.
KUPW:09:39:42.698: 1: In procedure SEND_MSG. Fatal=0
KUPW:09:39:42.698: 1: KUPC$QUEUE_INT.SEND called.
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
kwqberlst rqan->lascn_kwqiia > 0 block
kwqberlst rqan->lascn_kwqiia 7
kwqberlst ascn -90145310 lascn 22
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
KUPW:09:39:42.699: 1: KUPC$QUEUE_INT.SEND returned.
KUPW:09:39:42.699: 1: Total estimation using BLOCKS method: 2.812 GB
KUPW:09:39:42.699: 1: In procedure CONFIGURE_METADATA_UNLOAD
KUPW:09:39:42.699: 1: Phase: WORK_PHASE Filter Name: BEGIN_WITH Filter Value:
KUPW:09:39:42.699: 1: DBMS_METADATA.OPEN11.2.0.0.0 called.
KUPW:09:39:42.837: 1: DBMS_METADATA.OPEN11.2.0.0.0 returned. Source handle: 200001
KUPW:09:39:42.837: 1: DBMS_METADATA.SET_FILTER called. metadata_phase: WORK_PHASE
KUPW:09:39:42.837: 1: DBMS_METADATA.SET_FILTER returned. In function GET_NOEXP_TABLE
KUPW:09:39:42.847: 1: DBMS_METADATA.SET_PARSE_ITEM called.
KUPW:09:39:42.964: 1: DBMS_METADATA.SET_PARSE_ITEM returned.
KUPW:09:39:42.964: 1: DBMS_METADATA.SET_COUNT called.
KUPW:09:39:42.967: 1: DBMS_METADATA.SET_COUNT returned.
KUPW:09:39:42.967: 1: KUPF$FILE.OPEN_CONTEXT called.
KUPW:09:39:42.967: 1: KUPF$FILE.OPEN_CONTEXT returned.
KUPW:09:39:42.968: 1: DBMS_METADATA.FETCH_XML_CLOB called. Handle: 200001
*** 2011-09-20 09:40:01.798
KUPW:09:40:01.798: 1: DBMS_METADATA.FETCH_XML_CLOB returned.
KUPW:09:40:01.798: 1: Object seqno fetched:
KUPW:09:40:01.799: 1: Object path fetched:
KUPW:09:40:01.799: 1: In procedure SEND_MSG. Fatal=0
KUPW:09:40:01.799: 1: In procedure COMPLETE_EXP_OBJECT
KUPW:09:40:01.799: 1: KUPF$FILE.FLUSH_LOB called.
KUPW:09:40:01.815: 1: KUPF$FILE.FLUSH_LOB returned.
KUPW:09:40:01.815: 1: In procedure UPDATE_TYPE_COMPLETION_ROW
KUPW:09:40:01.815: 1: Old Seqno: 226 New Path: PO Num: -5 New Seqno: 0
KUPW:09:40:01.815: 1: Object count: 1
KUPW:09:40:01.815: 1: 1 completed for 226
KUPW:09:40:01.815: 1: DBMS_METADATA.CLOSE called. Handle: 200001
KUPW:09:40:01.816: 1: DBMS_METADATA.CLOSE returned.
KUPW:09:40:01.816: 1: KUPF$FILE.CLOSE_CONTEXT called.
KUPW:09:40:01.820: 1: KUPF$FILE.CLOSE_CONTEXT returned.
KUPW:09:40:01.821: 1: In procedure SEND_MSG. Fatal=0
KUPW:09:40:01.821: 1: KUPC$QUEUE.TRANSCEIVE called.
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
kwqberlst rqan->lascn_kwqiia > 0 block
kwqberlst rqan->lascn_kwqiia 7
kwqberlst ascn -90145310 lascn 22
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 7
KUPW:09:40:01.827: 1: KUPC$QUEUE.TRANSCEIVE returned. Received 2012
KUPW:09:40:01.827: 1: DBMS_LOB.CREATETEMPORARY called.
KUPW:09:40:01.828: 1: DBMS_LOB.CREATETEMPORARY returned.
KUPW:09:40:01.828: 1: Process order range: 1..1
KUPW:09:40:01.828: 1: Method: 1
KUPW:09:40:01.828: 1: Parallel: 1
KUPW:09:40:01.828: 1: Creation level: 0
KUPW:09:40:01.830: 1: BULK COLLECT called.
KUPW:09:40:01.830: 1: BULK COLLECT returned.
KUPW:09:40:01.830: 1: In procedure BUILD_OBJECT_STRINGS
KUPW:09:40:01.836: 1: In procedure MOVE_DATA UNLOADing process_order 1 TABLE_DATA:"TIA"."ACC_PAYMENT_SPECIFICATION" <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
KUPW:09:40:01.839: 1: KUPD$DATA.OPEN called.
KUPW:09:40:01.840: 1: KUPD$DATA.OPEN returned.
KUPW:09:40:01.840: 1: KUPD$DATA.SET_PARAMETER - common called.
KUPW:09:40:01.843: 1: KUPD$DATA.SET_PARAMETER - common returned.
KUPW:09:40:01.843: 1: KUPD$DATA.SET_PARAMETER - flags called.
KUPW:09:40:01.843: 1: KUPD$DATA.SET_PARAMETER - flags returned.
KUPW:09:40:01.843: 1: KUPD$DATA.START_JOB called.
KUPW:09:40:01.918: 1: KUPD$DATA.START_JOB returned. In procedure GET_JOB_VERSIONThis is how I called expdp:
expdp system/xxxxxxxxx schemas=tia directory=expdp INCLUDE=TABLE:\" =\'ACC_PAYMENT_SPECIFICATION\'\" REUSE_DUMPFILES=Y LOGFILE=expdp:$LOGFILE TRACE=400300Hi there ...
I have read the note - thats where I found the link to the trace note 286496.1 - on now to setup a trace
But I still need an explanation for the methods (1,2,4 etc)
regards
Mette -
Best Practice for data pump or import process?
We are trying to copy existing schema to another newly created schema. Used export data pump to successfully export schema.
However, we encountered some errors when importing dump file to new schema. Remapped schema and tablespaces, etc.
Most errors occur in PL/SQL... For example, we have views like below in original schema:
CREATE VIEW *oldschema.myview* AS
SELECT col1, col2, col3
FROM *oldschema.mytable*
WHERE coll1 = 10
Quite a few Functions, Procedures, Packages and Triggers contain "*oldschema.mytable*" in DML (insert, select, update) statement, for exmaple.
Getting the following errors in import log:
ORA-39082: Object type ALTER_FUNCTION:"TEST"."MYFUNCTION" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"TEST"."MYPROCEDURE" created with compilation warnings
ORA-39082: Object type VIEW:"TEST"."MYVIEW" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"TEST"."MYPACKAGE" created with compilation warnings
ORA-39082: Object type TRIGGER:"TEST"."MYTRIGGER" created with compilation warnings
A lot of actual errors/invalid objects in new schema are due to:
ORA-00942: table or view does not exist
My question is:
1. What can we do to fix those errors?
2. Is there a better way to do the import with such condition?
3. Update PL/SQL and recompile in new schema? Or update in original schema first and export?
Your help will be greatly appreciated!
Thank you!I routinely get many (MANY) errors as follows and they always compile when I recompile using utlrp.
ORA-39082: Object type ALTER_FUNCTION:"TKCSOWNER"."RPTSF_WR_LASTOUTPUNCH" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"TKCSOWNER"."RPTSF_WR_REFPERIODENDFOREMP" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"TKCSOWNER"."RPTSF_WR_TAILOFFSECS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"TKCSOWNER"."FN_GDAPREPORTGATHERER" created with compilation warnings
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/ALTER_PROCEDURE
ORA-39082: Object type ALTER_PROCEDURE:"TKCSOWNER"."ABSENT_EXCEPTION" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"TKCSOWNER"."ACCRUAL_BAL_PROJ" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"TKCSOWNER"."ACCRUAL_DETAILS" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"TKCSOWNER"."ACCRUAL_SUMMARY" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"TKCSOWNER"."ACTUAL_SCHEDULE" created with compilation warnings
It works. In all my databases: peoplesoft, kronos, and others...
I should qualify that it may still be necessary to 'debug' specific problems, but most common typical problems are easily resolved using the utlrp.sql. The usual problems I run into are typically because of a database link that points to another database such as in a production environment that we firewall our test and development databases from linking to (for obvious reasons). -
Hi
I wanted to refresh my dev environment quickly..
As we also wanted to migrate from exp/imp to datapump, I tried these..
Only thing worked for me is impdp on network mode using remap schema.
1)First i wanted to implement expdp and impdp standard procedures(Full database export/import)
My expdp failed with the following error on a full export..
Pls see below:
C:\Documents and Settings\oracle2>expdp system/<p.w> full=Y directory=DATA_PUMP_DIR dumpfile=OAPFULL.dmp logfile=OAPFULL.log
Export: Release 11.1.0.7.0 - Production on Thursday, 26 April, 2012 16:12:49
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_FULL_02": system/******** full=Y directory=DATA_PUMP_DIR dumpfile=OAPFULL.dmp logfile=OAPFULL.log
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 4.351 GB
Processing object type DATABASE_EXPORT/TABLESPACE
Processing object type DATABASE_EXPORT/PASSWORD_VERIFY_FUNCTION
Processing object type DATABASE_EXPORT/PROFILE
Processing object type DATABASE_EXPORT/SYS_USER/USER
Processing object type DATABASE_EXPORT/SCHEMA/USER
Processing object type DATABASE_EXPORT/ROLE
Processing object type DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/CONTEXT
Processing object type DATABASE_EXPORT/SCHEMA/PUBLIC_SYNONYM/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31672: Worker process DW01 died unexpectedly.
Job "SYSTEM"."SYS_EXPORT_FULL_02" stopped due to fatal error at 16:14:562)As the above failed, I tried impdp with network_link import and full=y and its a different issue!
impdp system/<p.w> NETWORK_LINK=OAPLIVE.WORLD full=y logfile=OAPDRfull2.log table_exists_
action=REPLACE
Import: Release 11.1.0.7.0 - Production on Thursday, 26 April, 2012 13:36:01
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** NETWORK_LINK=OAPLIVE.WORLD full=y logfile=OAPDRfull2.log table_exists_action=REPLACE
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 4.670 GB
Processing object type DATABASE_EXPORT/TABLESPACE
ORA-31684: Object type TABLESPACE:"SYSAUX" already exists
*************lots more of object already exists errors here............(space limit so cant paste)***************
ORA-31684: Object type SYNONYM:"GEOPROD"."EXT_POSTAIM_PRESORT_61" already exists
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.DISPATCH_WORK_ITEMS [SYNONYM:"GEOPROD"."EXT_POSTAIM_PRESORT_61"]
ORA-31600: invalid input value 200001 for parameter HANDLE in function CLOSE
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA", line 569
ORA-06512: at "SYS.DBMS_METADATA", line 4731
ORA-06512: at "SYS.DBMS_METADATA", line 792
ORA-06512: at "SYS.DBMS_METADATA", line 4732
ORA-06512: at "SYS.KUPW$WORKER", line 2718
ORA-03113: end-of-file on communication channel
ORA-02055: distributed update operation failed; rollback required
ORA-02063: preceding lines from OAPLIVE.WORLD
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7858
----- PL/SQL Call Stack -----
object line object
handle number name
242F2F2C 18256 package body SYS.KUPW$WORKER
242F2F2C 7885 package body SYS.KUPW$WORKER
242F2F2C 8657 package body SYS.KUPW$WORKER
242F2F2C 1545 package body SYS.KUPW$WORKER
241DDF3C 2 anonymous block
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA []
ORA-31642: the following SQL statement fails:
SELECT unique ku$.seq# from sys.metanametrans$ ku$ WHERE ku$.htype='DATABASE_EXPORT' AND ku$.model='ORACLE' AND NOT ( ku$.seq#>=(select a.seq# from sys.metanametrans$ a where
a.model='ORACLE' and a.htype='DATABASE_EXPORT' and a.name ='DATABASE_EXPORT/SCHEMA/SYNONYM')) order by ku$.seq#
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA_INT", line 5002
ORA-01427: single-row subquery returns more than one row
ORA-06512: at "SYS.DBMS_
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 7853
----- PL/SQL Call Stack -----
object line object
handle number name
242F2F2C 18256 package body SYS.KUPW$WORKER
242F2F2C 7885 package body SYS.KUPW$WORKER
242F2F2C 2744 package body SYS.KUPW$WORKER
242F2F2C 8523 package body SYS.KUPW$WORKER
242F2F2C 1545 package body SYS.KUPW$WORKER
241DDF3C 2 anonymous block
Job "SYSTEM"."SYS_IMPORT_FULL_01" stopped due to fatal error at 13:39:48So its basically these 2 issues I want to know how to fix.
1-expdp error cause and fix
2-impdp error cause and fix -Also how to avoid object alreay exists error?
Also for example the package etc. is the same name..but i want new package from LIVE so it means if the same name package, view, etc is there, it wouldnt get updated?
Any way to overcome this?
I need it exactly same as LIVE...(with a few exceptions which is small enough i can do after impdp finishes fine)
Pleaseeeeeeee help!!
Thanks&Regards.......Hi..
Thanks for the links..I applied the tips on each of them but it didnt work.
Also my database is 11g so it is not true that this happens on 10g only.
Things tried:
1)I tried with different values on parallel parameter but same error
2)I applied the following:
alter system set open_cursors=1024 scope=spfile;
alter system set "_optimizer_cost_based_transformation"=off;
commit;
The 3rd link was bit better
I tried to find out where exactly the error was causesusing
expdp attach =SYS_EXPORT_FULL_03
But I cant figure out what the object : PUBLIC
oracle/context/isearch/GetPage
is..?
Does this needs to be excluded from the export?if so, how?
Can someone help how to fix the error now?
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31672: Worker process DW01 died unexpectedly.
Job "SYSTEM"."SYS_EXPORT_FULL_03" stopped due to fatal error at 11:29:32
C:\Documents and Settings\ora2>expdp attach=SYS_EXPORT_FULL_03
Export: Release 11.1.0.7.0 - Production on Tuesday, 01 May, 2012 11:35:38
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Job: SYS_EXPORT_FULL_03
Owner: SYSTEM
Operation: EXPORT
Creator Privs: TRUE
GUID: 8499C802F52A414A8BCACE552DDF6F11
Start Time: Tuesday, 01 May, 2012 11:37:56
Mode: FULL
Instance: geooap
Max Parallelism: 1
EXPORT Job Parameters:
Parameter Name Parameter Value:
CLIENT_COMMAND system/******** parfile=h:\datapump\oapfull.par
State: IDLING
Bytes Processed: 0
Current Parallelism: 1
Job Error Count: 0
Dump File: H:\datapump\oapfull.dmp
bytes written: 4,096
Worker 1 Status:
Process Name: DW01
State: UNDEFINED
Object Schema: PUBLIC
Object Name: oracle/context/isearch/GetPage
Object Type: DATABASE_EXPORT/SCHEMA/PUBLIC_SYNONYM/SYNONYM
Completed Objects: 766
Total Objects: 766
Worker Parallelism: 1 -
Stupid question about import/export
Hi All,
i'm banging my head against the wall :) :)
i have one database (oracle 10g) , the database is called ORAPD
in this database lives a user called WFAT
ORAPD -- WFAT
now i create 3 another users: WFATG , WFAUTOG, WFPATG
Now i want to import all data, objects, index,sequences etc from WFAT to each one of the other 3 users
ORAPD -- WFAT
-- WFATG (new user with objects from wfat)
-- WFAUTOG (new user with objects from wfat)
-- WFPATG (new user with objects from wfat)
this is want i've done.
export wfat objects, connected with user system with expdp
import wfaobjects to each one of the new 3 users with impdp , remapping schemas and tablespaces
f:\impdp system/passwordXXX schemas=wfat remap_schema=wfat:wfautog remap_ta
blespace=tbs_wfatg_tab:tbs_wfautog_tab remap_tablespace=tbs_wfatg_idx:tbs_wfauto
g_idx remap_tablespace=tbs_wfatg_xml:tbs_wfautog_xml status=60 dumpfile=exp_wfat
g_20100421.dmp parallel=2 directory=dumpdirdd
The problem:
i have WFAT tables with triggers that belong to WFATG , WFPATG and WFAUTOG users !!!
why ???
Best regards
Rui MadalenoHi Paul,
thanks for you reply
I have followed your suggestion and removed the shemas=wfat option from the impdp command.
Here are the steps:
1) create the user wfautog
Note that , before the import i've created the tablespaces and the wfautog user:
CREATE USER WFAUTOG
IDENTIFIED BY xxxxxx
DEFAULT TABLESPACE TBS_WFAUTOG_TAB
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for WFAUTOG
GRANT CONNECT TO WFAUTOG;
GRANT RESOURCE TO WFAUTOG;
ALTER USER WFAUTOG DEFAULT ROLE ALL;
-- 1 System Privilege for WFAUTOG
GRANT UNLIMITED TABLESPACE TO WFAUTOG;
2) import data:
f:\impdp system/passwordXXX remap_schema=wfat:wfautog remap_ta
blespace=tbs_wfatg_tab:tbs_wfautog_tab remap_tablespace=tbs_wfatg_idx:tbs_wfauto
g_idx remap_tablespace=tbs_wfatg_xml:tbs_wfautog_xml status=60 dumpfile=exp_wfat
g_20100421.dmp parallel=2 directory=dumpdirdd
After that i detect the following problems :( :(
1) There are no sequences in the wfautog schema
2) There are triggers owned by wfautog "pointing" to wfat tables
Can you help me ?
This is the log file from impdp:
===================
Import: Release 10.1.0.2.0 - Production on Thursday, 22 April, 2010 8:27
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** remap_schema=wfatg:wfautog remap_tablespace=tbs_wfatg_tab:tbs_wfautog_tab remap_tablespace=tbs_wfatg_idx:tbs_wfautog_idx remap_tablespace=tbs_wfatg_xml:tbs_wfautog_xml status=60 dumpfile=exp_wfatg_20100421.dmp parallel=2 directory=dumpdir
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"WFAUTOG" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PASSWORD_HISTORY
Processing object type SCHEMA_EXPORT/SE_PRE_SCHEMA_PROCOBJACT/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "WFAUTOG"."LOGSTRANSFERENCIAS" 46.60 MB 866193 rows
. . imported "WFAUTOG"."PASTAS" 35.89 MB 1273050 rows
. . imported "WFAUTOG"."PROCESSOS" 100.9 MB 422797 rows
. . imported "WFAUTOG"."DOCUMENTOSPROCESSOS" 24.59 MB 345854 rows
. . imported "WFAUTOG"."TRANSFERENCIA_AS400" 18.09 MB 569333 rows
. . imported "WFAUTOG"."CODIGOS_POSTAIS" 8.258 MB 195516 rows
. . imported "WFAUTOG"."ANOTACOESPROCESSOS" 6.840 MB 71609 rows
. . imported "WFAUTOG"."ALERTASPROCESSOS" 4.533 MB 58447 rows
. . imported "WFAUTOG"."PROCESSO_CLINICO" 1.740 MB 27211 rows
. . imported "WFAUTOG"."COMUNICACAO_PRESTADOR" 1.171 MB 11955 rows
. . imported "WFAUTOG"."TEXTOSAUTPROCESSOS" 1018. KB 6784 rows
. . imported "WFAUTOG"."PS_TXN" 310.5 KB 100 rows
. . imported "WFAUTOG"."TAREFA" 716.2 KB 15227 rows
. . imported "WFAUTOG"."MOTIVOS_COMUNICACAO" 205.7 KB 18455 rows
. . imported "WFAUTOG"."AUTORIZACOESPROCESSOS" 152.8 KB 1904 rows
. . imported "WFAUTOG"."AGENDA_UTILIZADOR" 96.92 KB 2647 rows
. . imported "WFAUTOG"."TRIBUNAL_TRABALHO" 104.2 KB 987 rows
. . imported "WFAUTOG"."AGENDA_DOCS" 65.59 KB 4422 rows
. . imported "WFAUTOG"."DOC_COM_PRESTADOR" 88.28 KB 6479 rows
. . imported "WFAUTOG"."PRESTADOR" 53.29 KB 354 rows
. . imported "WFAUTOG"."TRIBUNAL" 47.07 KB 304 rows
. . imported "WFAUTOG"."ACORDAO" 5.281 KB 3 rows
. . imported "WFAUTOG"."ADVOGADO" 6.453 KB 38 rows
. . imported "WFAUTOG"."AGENDA_ALERTAS" 10.50 KB 387 rows
. . imported "WFAUTOG"."AGENDA_AUTORIZACOES" 5.632 KB 31 rows
. . imported "WFAUTOG"."EVT_AGENDA" 28.15 MB 600474 rows
. . imported "WFAUTOG"."XML_PROC_AS400" 0 KB 0 rows
. . imported "WFAUTOG"."AGENDA_TAREFAS" 6.273 KB 77 rows
. . imported "WFAUTOG"."AREASGESTAO" 6.945 KB 19 rows
. . imported "WFAUTOG"."AREASGESTAOUTILIZADOR" 15.14 KB 919 rows
. . imported "WFAUTOG"."CONCELHOS" 12.00 KB 308 rows
. . imported "WFAUTOG"."CONFIGURACOES" 11.54 KB 117 rows
. . imported "WFAUTOG"."CONTACTOS_ESCRITORIO" 7.484 KB 57 rows
. . imported "WFAUTOG"."CORRESPONDENCIA_MODELOS" 6.789 KB 15 rows
. . imported "WFAUTOG"."DISTRITOS" 5.757 KB 29 rows
. . imported "WFAUTOG"."ESCRITORIOS" 11.67 KB 61 rows
. . imported "WFAUTOG"."ESCRITORIOS_UTILIZADOR" 7.609 KB 139 rows
. . imported "WFAUTOG"."ESTADOS_ALERTA" 5.281 KB 3 rows
. . imported "WFAUTOG"."ESTADOS_AUTORIZACAO" 5.328 KB 5 rows
. . imported "WFAUTOG"."ESTADO_CLINICO" 5.328 KB 8 rows
. . imported "WFAUTOG"."ESTADO_COMUNICACAO" 5.390 KB 8 rows
. . imported "WFAUTOG"."ESTADO_EXAME" 5.289 KB 3 rows
. . imported "WFAUTOG"."ESTADO_JUNTA_MEDICA" 5.289 KB 3 rows
. . imported "WFAUTOG"."ESTADO_PROCESSO" 5.312 KB 5 rows
. . imported "WFAUTOG"."ESTADO_PROC_CLINICO" 5.281 KB 3 rows
. . imported "WFAUTOG"."ESTADO_REEMBOLSO" 5.734 KB 6 rows
. . imported "WFAUTOG"."ESTADO_TAREFA" 5.312 KB 5 rows
. . imported "WFAUTOG"."ESTADO_TC" 5.281 KB 3 rows
. . imported "WFAUTOG"."ESTADO_TENT_CONC" 5.335 KB 4 rows
. . imported "WFAUTOG"."ESTADO_TT" 5.296 KB 4 rows
. . imported "WFAUTOG"."EVT_EVENTO" 5.906 KB 8 rows
. . imported "WFAUTOG"."EVT_GRUPO" 5.257 KB 1 rows
. . imported "WFAUTOG"."FAX_QUEUE" 8.976 KB 43 rows
. . imported "WFAUTOG"."FORMATOSDOCUMENTO" 5.398 KB 10 rows
. . imported "WFAUTOG"."FORMA_CAUCAO" 5.304 KB 3 rows
. . imported "WFAUTOG"."FUNCIONALIDADES" 6.140 KB 9 rows
. . imported "WFAUTOG"."FUNCIONALIDADES_PERFIS" 5.484 KB 24 rows
. . imported "WFAUTOG"."GENERIC_ERRORS" 9.328 KB 33 rows
. . imported "WFAUTOG"."GRUPOS_LOG" 5.476 KB 12 rows
. . imported "WFAUTOG"."HOSPITAL_CLINICA" 20.82 KB 124 rows
. . imported "WFAUTOG"."HOSP_CLIN_REDE_MED" 6.476 KB 124 rows
. . imported "WFAUTOG"."INDISPUTILIZADOR" 9.234 KB 58 rows
. . imported "WFAUTOG"."INSTANCIA" 5.281 KB 3 rows
. . imported "WFAUTOG"."IP_DEFINIDA" 5.265 KB 4 rows
. . imported "WFAUTOG"."IP_PRESUMIVEL" 5.273 KB 4 rows
. . imported "WFAUTOG"."MEDICO" 16.21 KB 236 rows
. . imported "WFAUTOG"."MED_HOSP_CLIN" 5.265 KB 4 rows
. . imported "WFAUTOG"."MOTIVOS_POR_TENT_CONC" 5.257 KB 2 rows
. . imported "WFAUTOG"."MOTIVOS_TIPO_PRESTADOR" 6.929 KB 26 rows
. . imported "WFAUTOG"."MOTIVO_TENT_CONC" 5.414 KB 6 rows
. . imported "WFAUTOG"."NOME_TAREFA" 7.125 KB 27 rows
. . imported "WFAUTOG"."ORIGEM_EXAME" 5.265 KB 2 rows
. . imported "WFAUTOG"."PERFIS" 5.375 KB 8 rows
. . imported "WFAUTOG"."PERFISUTILIZADOR" 11.10 KB 272 rows
. . imported "WFAUTOG"."PERITO_MEDICO" 19.53 KB 307 rows
. . imported "WFAUTOG"."PLAN_TABLE" 18.26 KB 10 rows
. . imported "WFAUTOG"."PROCESSOSABERTOS" 5.617 KB 20 rows
. . imported "WFAUTOG"."RAMOS" 6.085 KB 11 rows
. . imported "WFAUTOG"."REDE_MEDICA" 5.375 KB 6 rows
. . imported "WFAUTOG"."REGIME_ASSISTENCIA" 5.273 KB 2 rows
. . imported "WFAUTOG"."REPRESENTANTE" 9.929 KB 97 rows
. . imported "WFAUTOG"."REPRESENTANTE_TEMP" 10.07 KB 8 rows
. . imported "WFAUTOG"."RESULTADO_SENTENCA" 5.281 KB 2 rows
. . imported "WFAUTOG"."TENTATIVA_CONCILIACAO" 8.218 KB 3 rows
. . imported "WFAUTOG"."TIPOSDOCUMENTO" 7.859 KB 71 rows
. . imported "WFAUTOG"."TIPOS_PASTA" 6.304 KB 6 rows
. . imported "WFAUTOG"."TIPO_CAUCAO" 5.296 KB 3 rows
. . imported "WFAUTOG"."TIPO_EXAME" 5.312 KB 3 rows
. . imported "WFAUTOG"."TIPO_HOSPITALCLINICA" 5.312 KB 3 rows
. . imported "WFAUTOG"."TIPO_IP" 5.343 KB 7 rows
. . imported "WFAUTOG"."TIPO_PRESTADOR" 5.343 KB 5 rows
. . imported "WFAUTOG"."TIPO_TRIBUNAL" 5.289 KB 2 rows
. . imported "WFAUTOG"."TRANSPORTE_ESPECIAL" 5.312 KB 5 rows
. . imported "WFAUTOG"."TRIBUNAL_CIVEL" 25.10 KB 18 rows
. . imported "WFAUTOG"."UTILIZADORES" 22.97 KB 196 rows
. . imported "WFAUTOG"."ACTUALIZACAO_LOG" 0 KB 0 rows
. . imported "WFAUTOG"."ACTUALIZACOESAS400" 0 KB 0 rows
. . imported "WFAUTOG"."AGENCIASFAX" 0 KB 0 rows
. . imported "WFAUTOG"."AREASPERFIL" 0 KB 0 rows
. . imported "WFAUTOG"."EXAMES" 0 KB 0 rows
. . imported "WFAUTOG"."FERIADOS" 0 KB 0 rows
. . imported "WFAUTOG"."JUNTA_MEDICA" 0 KB 0 rows
. . imported "WFAUTOG"."LOGSLOGINS" 0 KB 0 rows
. . imported "WFAUTOG"."LOGSPROCESSOS" 0 KB 0 rows
. . imported "WFAUTOG"."PERFISAREA" 0 KB 0 rows
. . imported "WFAUTOG"."PERMISSOES" 0 KB 0 rows
. . imported "WFAUTOG"."PKGLOG_TAB" 0 KB 0 rows
. . imported "WFAUTOG"."SENTENCA" 0 KB 0 rows
. . imported "WFAUTOG"."TRANSF_DEFINITIVAS_ERRORS" 0 KB 0 rows
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/PACKAGE/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/FUNCTION/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PROCEDURE/GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."DEVOLVE_1_PARTICIP_PROC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."DEVOLVE_NOME_PRESTADOR_PC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."DEVOLVE_ULTIMO_RELATMED_PROC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"WFAUTOG"."SMS_FAX_HANDLER" created with compilation warnings
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."DAR_TOMAR_CONHECIMENTO_HANDLER" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."FAX_COMPROVATIVO_HANDLER" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."SEND_FAX_CORRESPONDENCIA" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."TROCA_GESTOR" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"WFAUTOG"."WFAT_JOB_ENGINE_HANDLER" created with compilation warnings
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."SINISTRO_WEBSERVICE_HANDLER" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."TRANSFERE_DEFINITIVO_PKG" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."VERIFICA_INDISPONIBILIDADES" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."ACTIVACAO_AGENDA_PKG" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."CLASSIFICACAO_PKG" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"WFAUTOG"."PKG_UTILS" created with compilation warnings
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_INS_ALERTAS_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_INS_ALERTAS_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_UPDT_AUT_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."AFT_UPDT_AUT_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INSERT_AGENDA_UTIL_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INSERT_AGENDA_UTIL_TRG" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ACOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ACOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ADV" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ADV" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ALRT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ALRT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ANOT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ANOT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_AUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_AUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_CPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_CPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_DOCP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_DOCP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EAUT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECOM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ECOM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EJM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EJM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EPROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EPROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ESTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ESTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_ETT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EXM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_EXM" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FCAU" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FCAU" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FUNC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_FUNC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_GRPL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_GRPL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_HOSP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_HOSP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INDISP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INDISP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_INS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPD" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPD" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_IPP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_JMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_JMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LGP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LGP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LOGT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_LOGT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_MTP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_NTF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_NTF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_OEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_OEX" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PCL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PCL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERF" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERFS_UTIL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PERFS_UTIL" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PROC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PST" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PST" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PTR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_PTR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RAS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RAS" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_REP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_REP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RMED" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RSEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_RSEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_SEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_SEN" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TAR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TAR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TCONC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TCONC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TESP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TESP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPA" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPA" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPE" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPE" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPIP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPIP" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TPR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRANSF_AS400" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRANSF_AS400" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRIB" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TRIB" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TXT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_INS_TXT" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_UPD_AGENDA_UTILIZADOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."BEF_UPD_AGENDA_UTILIZADOR" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_BEF_INS_ESC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_BEF_INS_ESC" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_AFT_INS_AGENDA_UTI" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_AFT_INS_AGENDA_UTI" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_BEF_DEL_AGENDA_UTI" created with compilation warnings
ORA-39082: Object type TRIGGER:"WFAUTOG"."TRIG_EVT_BEF_DEL_AGENDA_UTI" created with compilation warnings
Processing object type SCHEMA_EXPORT/TABLE/INDEX/SE_TBL_FBM_INDEX_INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/SE_TBL_FBM_IND_STATS/INDEX_STATISTICS
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 150 error(s) at 08:35
Regards
Rui Madaleno -
Hi,
O/S : HP Unix
DB : 11.2.0.3
Server Source_A : Let's say i have user with the name 'Rob' and this user has been assigned a role 'MY_SRC_ROLE' .
I developed a table under rob schema and granted access to this table via role
GRANT DELETE, INSERT, SELECT, UPDATE ON rob.emp TO MY_SRC_ROLE;
I have 100 more users & they have been granted this role 'MY_SRC_ROLE'. These 100 users can now access emp table via Role 'MY_SRC_ROLE' without any issues.
Now i took a datapump export & performed datapump import on target server which is also HP Unix with 11.20.3 . On target server i have user 'JACK' and a role called 'MY_WORK_ROLE'. 5000 users have been granted 'MY_WORK_ROLE' on this server.
I have used remap tablespace clause & remap schema clause in datapump import script. Once i performed an import , due to schema remap , i can see JACK now owns table 'emp', however grants are still not there, I tried searching on google & oracle documentation, if somehow we can remap ROLE GRANTS also while doing datapump imp, but i couldn't find supporting syntax. Am i missing something or probably can i assume datapump import is not capable to handle this particular scenario ? I was able to do it by manipulating sqlfile and replacing role name in that but i am looking for a sol. within datapump itself.
So bottom line how can grants assigned to ROLE 'X' be transferred to 'Role Y' via datapump import.
Let me know, if any any additional details are required.
-LearnerHi,
AFAIK, you can not remap/rname the roles. you can generate the Dynamic script and Apply on Target
something like that
spool role_target.sql
select 'grant '|| PRIVILEGE || ' MY_WORK_ROLE;' from dba_sys_privs where GRANTEE='MY_SRC_ROLE';
spool off
@role_target.sql
HTH -
Create procedure in different scheam
Hi Team,
I have a requirement like i have 2 schema like Schema A and Schema B in Schema A have procedure like SP_EMP_DETAILS this procedure need to create in Schema B as will
present we are using manual process copy the script from Schema A and past in Schema B and execute please provide any idea for wring the code and execute in Schema B.
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
"CORE 11.2.0.3.0 Production"
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
Thanks in Advance.You could remap schema. Try something like this
create or replace function get_ddl_schema_transform
p_object_type in varchar2,
p_object_name in varchar2,
p_old_schema in varchar2,
p_new_schema in varchar2
return clob
as
l_handle number;
l_transform number;
l_script clob;
begin
l_handle := dbms_metadata.open(p_object_type);
l_transform := dbms_metadata.add_transform
l_handle
, 'MODIFY'
dbms_metadata.set_remap_param
l_transform
, 'REMAP_SCHEMA'
, p_old_schema
, p_new_schema
l_transform := dbms_metadata.add_transform
l_handle
, 'DDL'
dbms_metadata.set_filter
l_handle
, 'SCHEMA'
, p_old_schema
dbms_metadata.set_filter
l_handle
, 'NAME'
, p_object_name
l_script := dbms_metadata.fetch_clob(l_handle);
dbms_metadata.close(l_handle);
return l_script;
end; -
Is there an option to be specified in EXPDP(Data Pump Export) and IMPDP(Data Pump import) to export/import the packages, procedures from one user/schema to the other with in the same database?
You can use include parameter and the remap schema parameter.
Expdp user/password include=procedure,packages ...
If you have a loopback dblink, then you can do it all pin one command without creating a dump file. There is no expdp required. Do this
Impdp user/password network_link=your_loopback_dblink include=package,procedure remap_schema=old:new schemas=old ...
Hope this helps
Dean -
How to import dumpfile different tablespace using older import utility (Not impdp utility)?
ThanksNikolay Ivankin wrote:
Øyvind Isene wrote:
Create the new tablespace in target database, then create the user with default tablespace set to this and a with quota on it. When doing import, use fromuser=... and touser=... if the schema names differ. E.g.Remapping schema is not that OP've asked. He needs to remap tablespace, which is used under DataPump, but not in traditional imp.
1st way - use another DB and reexport with the help of datapump.
2nd way - create tbs(use existing) and assign unlimited quota to user you want to use for import. Revoke quota for others TBS.
Then all new data will be in the TBS you want. But if under this user will be activity - this activity will be saved also in the TBS.It was not clear to me that this was for the same user in the same database. If the user just wants to move tables and indexes from one tablespace to another for the same user/database he can just alter table ... move and alter index ... rebuild. With re-import to the same user, the objects must be dropped first, seems a bit more risky.
Anyway, we forgot to ask the most important question: why ? -
Prevent imports to sys and system users
I work at a company who develops an Application the uses an Oracle database. Many times we receive a full system export. I want to prevent my users from importing all the schema's, and just import from the schema that contains our data. Since the user name of the export is different from the user that does the import, I have granted them the IMP_FULL_DATABASE right. Almost all our customers use the same name for the schema, so if we want to look at the data of more then one customer, we need to import to another schema.
I am running two test servers, one for Oracle 10 and one for Oracle 11 on Oracle Linux. And I am already using one separate account to let them import and export the data, and to create the user.
Is there a way to prevent users from importing to the system, sys and other oracle schema's, without limiting schema imports of other Oracle servers?If you know which schema data you want to import into your database from the export dump , you can use shema leavel import . Also if you are using datapump you can use remap schema option.
Thanks and Regards,
Satish.G.S
http://gssdba.wordpress.com -
Trying to auto generate roles and privileges
Greetings All,
Oracle Enterprise 11g v11.2.0.1.0 on Windows Server 2008
I have a database with many schemas. One of the schemas is referred to as the CM_MASTER schema in that it has been granted the following: dba, create user, drop user, alter user, create any table, select any table, and a few others, all with the “with admin option” clause.
We have developers that need select only access to the tables and views of the non-master schemas. My plan was to create a unique ROLE for each schema, then grant select on each table and view in that schema to that unique role. Then grant the appropriate role(s) to each developer hence giving them read only access.
I can accomplish the above manually while logged on as the CM_MASTER schema.
I am trying to create a procedure owned and executed only by the CM_MASTER schema that creates a new role and then grants to that role. The procedure accepts a parameter containing the user name of the target schema. The procedure is able to create the role (create role scott_r) successfully.
However, I am getting an insufficient privileges error (see below) after the role has been created, when trying to issue the “grant select on scott.some_table to scott_r” command via "execute immediate".
Any ideas what privilege(s) the CM_MASTER user needs in order to be able to issue the grant(s) to the role?
Error message below:
exec gen_schema_role('scott');
Error report:
ORA-01031: insufficient privileges
ORA-06512: at "CM_MASTER.GEN_SCHEMA_ROLE", line 30
ORA-06512: at line 1
01031. 00000 - "insufficient privileges"
The procedure code is below:
The utl_file.put_line commands were added for debugging but nothing gets output.
When the "execute immediate" lines are commented out, the output from the utl_file.put_line commands displays the correct SQL create and grant statements.
create or replace
procedure gen_schema_role(p_db_user in varchar)
as
v_role_name varchar2(30);
v_bat_out utl_file.file_type;
cursor get_object_names is
select object_name from dba_objects
where owner = upper(p_db_user)
and object_type in ('TABLE','VIEW')
and status = 'VALID'
and object_name not like 'DR$%'
and object_name not like 'XT%';
begin
v_bat_out := utl_file.fopen('SR_BACKUP', 'Create_Roles.sql', 'W');
v_role_name := substr(p_db_user,1,28) || '_r';
utl_file.put_line(v_bat_out, ' ');
utl_file.put_line(v_bat_out, 'create role '||v_role_name);
execute immediate 'create role '||v_role_name; <<-- This seems to work, the role gets created
for a in get_object_names
loop
utl_file.put_line(v_bat_out,' grant select on ' || p_db_user || '.' || a.object_name || ' to ' || v_role_name);
execute immediate 'grant select on ' || p_db_user || '.' || a.object_name || ' to ' || v_role_name;
end loop;
utl_file.fclose(v_bat_out);
end gen_schema_role;
Thanks,
Snydssb92075,
I just tried, and YES the SQL is able to apply the "grant select" statements to the newly created role.
I wanted to call this new procedure from the procedure that creates a new user by scheduling a job to perform an IMPDP job to import a base schema (using the remap schema clause).
Any suggestions how to automate generating this role?
Thanks,
Snyds -
How to impdp usera.table1 into userb.table2 with a query...
Greetings
Environment:
Oracle 11.2.0.3 EE on Solaris
I have a full table export of USERA.TABLE1 and I want to import a portion of that table into USERB.TABLE2 using impdp.
I have tried several versions of my parfile but have not yet been successful. The import succeeds but imports ALL rows of the source table and not just the ones filtered by the QUERY.
Here is the latest version of my parfile: (not sure if the '{code}' formatting is still valid so pardon me if it's not)
{code}
userid=system/**********
directory=data_pump_dir
dumpfile=table1.dmp
logfile=table1_impdp.log
tables=usera.table1
remap_table=usera.table1:userb.table2
remap_schema=usera:userb
table_exists_action=append
query=usera.table1:"where trunc(ACTIVE_DATE)=to_date('31-jul-2013','dd-mon-rrrr')"
{code}
There is something wrong with the QUERY statement but I can't get the syntax correct.
ACTIVE_DATE is a valid column in both tables.
Is the schema.tablename supposed to be the original source values (usera.table1) or the new target values (userb.table2)?
Any help is greatly appreciated!!
-garyGary,
Here is the right parfile. I'll explain the reasoning.
tables=orig_schema.orig_table
remap_table=orig_schema.orig_table:new_table
remap_schema=orig_schema:new_schema
query=orig_schema.orig_table:"where rownum < 10"
The tables= parameter is a filter which needs to be applied to the existing dumpfile. It is done first regardless of which parameter you enter first on your command. So, since no remap has taken place yet, all Data Pump knows about is the original information.
remap_table - takes an optional original schema then an optional . then the required original table name. Then the required : and then just a new table name, NOT NEW_SCHEMA.NEW_TABLE.
In your case, you are also remapping the schema, so you need a remap schema= old_schema:new_schema
The query is also verified before any remapping is done so you need to specify the original information here.
Hope this helps.
Dean -
ORA-39122: Unprivileged users may not perform REMAP_SCHEMA remappings
hi experts i m facing ORA-39122: Unprivileged users may not perform REMAP_SCHEMA remappings error while importing schema level backup the have below proviliges
CREATE USER T24EXP
IDENTIFIED BY VALUES 'A8BE03AC28E87FE6'
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
GRANT CONNECT TO T24EXP;
GRANT RESOURCE TO T24EXP;
GRANT EXP_FULL_DATABASE TO T24EXP;
GRANT IMP_FULL_DATABASE TO T24EXP;
ALTER USER T24EXP DEFAULT ROLE ALL;
GRANT UNLIMITED TABLESPACE TO T24EXP;
GRANT READ, WRITE ON DIRECTORY SYS.DMP_EXP TO T24EXP;
GRANT READ, WRITE ON DIRECTORY SYS.DUMP_BKUP TO T24EXP;
GRANT READ, WRITE ON DIRECTORY SYS.SIT_DMP_EXP TO T24EXP;
what is the possible reason of getting this errorI also faced same problem.
After putting both datapump_exp_full_database & datapump_imp_full_database i could not remap schema & tablespace (I think IMPORT_FULL_DATABASE not a privilege it should be IMP_FULL_DATABASE ).
To resolve the problem I grant DBA to the user. (I think this is reasonable to give enough power to get access on other's schema & tablespace).
If anybody has better solution please inform.
-Obaid
Maybe you are looking for
-
Problem purchasing Skype premium
I am having serious difficulties purchasing Skype premium. Following my participation in an academic congress in China last year, my Skype account has accidently become associated with Skype's Chinese partner Tom Online. When I now try to purchase S
-
got a macbook pro. runs FFox 4.0.1 Daily i get prompt says "update FFox". I click it and it says"connecting to server" forever. have to close window. does this daily.
-
Hi i would use this to parse String to Date : public Date parseFromString(String dateString){ try { java.text.SimpleDateFormat formatter = new java.text.SimpleDateFormat("dd/MM/yy"); return formatter.parse(date
-
Dear All, we defined one section code for the cocd. the same section code we are using for all the bussiness places ( 4 no's). when i post a document with one business place with the section code it accepted the posting and remittence challan, bank c
-
I am using ION U Record EZ vinyl/tape converter and cannot upload content onto itunes
I am using ION U Record vinyl/tape converter which uses itunes. I can record the track but it does not upload content onto itunes. I have successfully transferred many songs but have now updated to a later version of itunes and can no longer upoload