Dbms_logstdby.instantiate_table error
Hi,
I'm getting the following error when trying to re-instantiate a table in a logical standby database:
SQL> exec dbms_logstdby.instantiate_table('<OWNER>',<TABLE>',<DB_LINK>');
BEGIN dbms_logstdby.instantiate_table('<OWNER>',<TABLE>',<DB_LINK>'); END;
ERROR at line 1:
ORA-31634: job already exists
ORA-06512: at "SYS.DBMS_LOGSTDBY", line 577
ORA-06512: at line 1
it seems that when you instantiate a table this way, oracle creates a Datapump import job with the default name 'SYS_IMPORT_TABLE_NN' where NN is a number between 00 and 99. When I checked the dba_datapump_jobs table, there were 100 entries for import jobs, all with a state of NOT RUNNING and number 00 - 99. When I tried to attach to one of these using impdp, the session closes saying the job completed successfully. Is this a bug? If so does anyone know of a fix for this, or can I just delete the old entries from dba_datapump_jobs?
Thanks! the package is valid but this worked:
EXECUTE DBMS_LOGSTDBY.INSTANTIATE_TABLE ( SCHEMA_NAME => 'HR', TABLE_NAME => 'TABLE', DBLINK => 'link_to_pid3728p' );
I had other privileges problems
ERROR at line 1:
ORA-31631: privileges are required
ORA-06512: at "SYS.DBMS_LOGSTDBY", line 664
ORA-06512: at line 1
this is what the alert log says:
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=32, OS id=7626
to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_TABLE_01', 'SYS', 'KUPC$C_1_20111121182352', 'KUPC$S_1_20111121182352', 0);
But i solved those problems doing this: "grant dba to hr;" "alter user hr default role dba;". I rolled that back after INSTANTIATE_TABLE .
Thanks a lot!!
Similar Messages
-
Create table on Logical Standby Database
Dear DBAs,
here is my situation;
1. My primary database (where the tables' owner is "ICC" having a DBA) is used for insert/update transactions.
2. The logical stdby DB (dataguard structure with MAX availability) is used to generate reports, after updating some tables owned by the same user "ICC". note that these tables are excluded from the replication.
3. The developers might need to create this kind of tables to generate another kind of reports.
The issue is that when the standby apply is enabled or disabled, the user ICC is not able to create a new table, it gives ORA-01031: insufficient privileges. note that it's not practical to ask the DBA to disable the "APPLY" at any table creation.
Do you have an idea about how to resolve.
My database is 10gR2 path.10.2.0.4.0 on Windows 2003
Thank you in advanceIf you stop applying log on the logical standby you can easily create a table over there. See oracle docs. The following list shows >how to re-create a table and restart SQL Apply on that table:
>
Stop SQL Apply:
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Ensure no operations are being skipped for the table in question by querying the DBA_LOGSTDBY_SKIP view:
SQL> SELECT * FROM DBA_LOGSTDBY_SKIP;
ERROR STATEMENT_OPT OWNER NAME PROC
N SCHEMA_DDL HR EMPLOYEES
N DML HR EMPLOYEES
N SCHEMA_DDL OE TEST_ORDER
N DML OE TEST_ORDER
Because you already have skip rules associated with the table that you want to re-create on the logical standby >database, you must first delete those rules. You can accomplish that by calling the DBMS_LOGSTDBY.UNSKIP >procedure. For example:
SQL> EXECUTE DBMS_LOGSTDBY.UNSKIP(stmt => 'DML', -
schema_name => 'HR', - object_name => 'EMPLOYEES');SQL> EXECUTE DBMS_LOGSTDBY.UNSKIP(stmt >=> 'SCHEMA_DDL', -
schema_name => 'HR', - object_name => 'EMPLOYEES');
Re-create the table HR.EMPLOYEES with all its data in the logical standby database by using the >DBMS_LOGSTDBY.INSTANTIATE_TABLE procedure. For example:
SQL> EXECUTE DBMS_LOGSTDBY.INSTANTIATE_TABLE(shema_name => 'HR', -
object-_name => 'EMPLOYEES', -
dblink => 'BOSTON');
Start SQL Apply:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;Regards. -
ORA-01403: no data found on LOGICAL STANDBY database
Hi ,
Logical Standby issue :
Oracle 10.2.0.2 enterprise edition .
M Working on LOGICAL Standby since 1 yrs but still i havent got this ......................................
I m getting countinuously no data foud errror on logical standby database .
I found the table causing the proble(db_logstdby_events) and skipped that table and instanciated table using bwlow package:
exec dbms_logstdby.instantiate_table (.......................................
but when i start apply process on logical standby it again give no data found for new table :
Even i tried to instantiate the table using EXPORT/IMPORT during down time but the same facing same problem .
As much as i known abt the error that is :
table1
id
10
20
30
Now if sql apply process on logical standby tries to performe the update transaction(for example) as belows
update table1 set id=100 where id=50;
above query will not be completed cos it will never find the values 50 which is not in table .Thts why this error comming ..
Now my worry is ... no users dare to change/make such changes on Logical standby .So if there is no changes in tables then sqll apply should get all the values to be needded for an update ......
watingggg guyssss/......Troubleshooting ORA-1403 errors with Flashback Transaction
In the event that the SQL Apply engine errors out with an ORA-1403, it may be possible to utilize flashback transaction on the standby database to reconstruct the missing data. This is reliant upon the undo_retention parameter specified on the standby database instance.
ORA-1403: No Data Found
Under normal circumstances the ORA-1403 error should not be seen in a Logical Standby environment. The error occurs when data in a SQL Apply managed table is modified directly on the standby database, and then the same data is modified on the primary database.
When the modified data is updated on the primary database and received by the SQL Apply engine, the SQL Apply engine verifies the original version of the data is present on the standby database before updating the record. When this verification fails, an ORA-1403: No Data Found error is thrown by Oracle Data Guard: SQL Apply.
The initial error
When the SQL Apply engine verification fails, the error thrown by the SQL Apply engine is reported in the alert log of the logical standby database as well as a record being inserted into the DBA_LOGSTDBY_EVENTS view. The information in the alert log is truncated, while the error is reported in it's entirety in the database view.
LOGSTDBY stmt: update "SCOTT"."MASTER"
set
"NAME" = 'john'
where
"PK" = 1 and
"NAME" = 'andrew' and
ROWID = 'AAAAAAAAEAAAAAPAAA'
LOGSTDBY status: ORA-01403: no data found
LOGSTDBY PID 1006, oracle@staco03 (P004)
LOGSTDBY XID 0x0006.00e.00000417, Thread 1, RBA 0x02dd.00002221.10
The Investigation
The first step is to analyze the historical data of the table that threw the error. This can be achieved using the VERSIONS clause of the SELECT statement.
SQL> select versions_xid
, versions_startscn
, versions_endscn
, versions_operation
, pk
, name
from scott.master
versions between scn minvalue and maxvalue
where pk = 1
order by nvl(versions_startscn,0);
VERSIONS_XID VERSIONS_STARTSCN VERSIONS_ENDSCN V PK NAME
03001900EE070000 3492279 3492290 I 1 andrew
02000D00E4070000 3492290 D 1 andrew
Depending upon the amount of undo retention that the database is configured to retain (undo_retention) and the activity on the table, the information returned might be extensive and the versions between syntax might need to be changed to restrict the amount of information returned.
From the information returned, it can be seen that the record was first inserted at scn 3492279 and then was deleted at scn 3492290 as part of transaction ID 02000D00E4070000. Using the transaction ID, the database should be queried to find the scope of the transaction. This is achieved by querying the flashback_transaction_query view.
SQL> select operation
, undo_sql
from flashback_transaction_query
where xid = hextoraw('02000D00E4070000');
OPERATION UNDO_SQL
DELETE insert into "SCOTT"."MASTER"("PK","NAME") values
('1','andrew');
BEGIN
Note that there is always one row returned representing the start of the transaction. In this transaction, only one row was deleted in the master table. The undo_sql column when executed will restore the original data into the table.
SQL> insert into "SCOTT"."MASTER"("PK","NAME") values ('1','andrew');
SQL> commit;
The SQL Apply engine may now be restarted and the transaction will be applied to the standby database.
SQL> alter database start logical standby apply; -
Issue while Instantiating a table in logical standby
I am trying to instantiate the tables in my logical standby and i am getting this error
ORA-39006: internal error
ORA-06512: at "SYS.DBMS_LOGSTDBY", line 636
ORA-06512: at line 1
i used the below command to instantiate the table
EXECUTE DBMS_LOGSTDBY.INSTANTIATE_TABLE('FLXUSER','JOB_ACTION', 'NGMES_PROD')
i have also provide all the required privilege i.e LOGSTDBY_ADMINISTRATOR and DBA.still i am getting the error.
In alertlog i found the Import struck warning as the job is getting struck.
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=31, OS id=4648
to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_TABLE_01', 'LH137', 'KUPC$C_1_20131218044529', 'KUPC$S_1_20131218044529', 0);
Wed Dec 18 04:47:54 2013
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=51, OS id=3076
to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_TABLE_01', 'LH137', 'KUPC$C_1_20131218044754', 'KUPC$S_1_20131218044754', 0);
Wed Dec 18 04:49:41 2013
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=52, OS id=4128
to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_TABLE_01', 'FLXUSER', 'KUPC$C_1_20131218044941', 'KUPC$S_1_20131218044941', 0);
which i think are just warning.
kindly help me outYes that could very well be the reason. You can try recompiling. If it does not fix, you can reload the whole datapump utility by using following metalink note:
How To Reload Datapump Utility EXPDP/IMPDP (Doc ID 430221.1) -
Logical standby instantiate table status
Oracle 10.2.0.4
Hello All,
I am instantiating a table in a logical standby, execute dbms_logstdby.instantiate_table ('schema','table','db_link'). The table contains 18 million records and has been running for about 1 hour. Is there any way I can check the status of this instantiation as far as how much data has been processed or time remaining.
Any help would be greatly appreciated!
Thank you,
Daveuser13129655 wrote:
Oracle 10.2.0.4
Hello All,
I am instantiating a table in a logical standby, execute dbms_logstdby.instantiate_table ('schema','table','db_link'). The table contains 18 million records and has been running for about 1 hour. Is there any way I can check the status of this instantiation as far as how much data has been processed or time remaining.
Any help would be greatly appreciated!
Thank you,
Davesince other session can not see uncommitted data, you can not do so directly.
query v$sess_io repeatedly to see that I/O is occurring. -
Logical Standby out of sync after archiver stuck (how to resync)
Hi,
I had an archiver stuck on my logical standby database for about 4 hours this night.
2 hours later my primary db also had an archiver stuck.
After solving the problem by repairing the backup mechanism and startup of the archivelog backup I realised
that some tables are out of sync.
How can I get back all things back in sync again?
DB: 11gR2 EE
OS: RedHat Linux 5.5
Thanks
941743Hi,
I don't sure have or not resyncronization whole schema, but you can use with PL/SQL as
Stop SQL Apply on logical standby database
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
on primary
SQL> begin
2> for t in (select table_name from db_tables where owner = '<your schema name>')
3> loop
4> DBMS_LOGSTDBY.INSTANTIATE_TABLE(shema_name => '<your schema name>', object_name => T.Table_name, dblink => '<you dblink name>');
5> end loop;
6>end;
Start SQL Apply on logical standby database
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;If you skip DML and DDL for your schema, then you must UNSKIP DML and DDL on this tables you must add following script to PL/SQL block before INSTANTIATE_TABLEs.
DBMS_LOGSTDBY.UNSKIP(stmt => 'DML', schema_name => '<your schema name>', object_name => T.Table_Name);
DBMS_LOGSTDBY.UNSKIP(stmt => 'DDL', schema_name => '<your schema name>', object_name => T.Table_Name);Regards
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on Sep 13, 2012 6:17 PM -
Logical Standby - Log Apply Error
Hi All
I have configured a 10.2.0.4 logical standby database (single instance) for RAC primary by LOG APPLY process stopped with this error:
ORA-01422: exact fetch returns more than requested number of rows.
Now I did run this command before creating logical standby: EXECUTE DBMS_LOGSTDBY.BUILD;
And I know that there are 80 tables which cannot be uniquely identified, which is fine by business.
Could you someone please tell how can I deal with this problem.
Regards
AmitI have configured a 10.2.0.4 logical standby database (single instance) for RAC primary by LOG APPLY process stopped with this error:
ORA-01422: exact fetch returns more than requested number of rows.
Now I did run this command before creating logical standby: EXECUTE DBMS_LOGSTDBY.BUILD;
And I know that there are 80 tables which cannot be uniquely identified, which is fine by business.
Could you someone please tell how can I deal with this problem. It looks like a Bug too, check this below note
*Bug 5889516 - Intermittently ORA-1422 logical standby errors [ID 5889516.8]* -
My two node RAC database Primary hangs upon executing SQL> exec DBMS_LOGSTDBY.BUILD; when creating a Logical Standby. I have stopped all the recovery processes on the Physical Standby. I have also taken down the instances on the RAC apart from the one I'm working on. Additionally not much info in the alert log...
Logminer Bld: Build started
Wed Jan 23 06:01:57 2013
ALTER SYSTEM SWITCH ALL LOGFILE start (UDSRED1)
Wed Jan 23 06:01:57 2013
ALTER SYSTEM SWITCH ALL LOGFILE complete (UDSRED1)
Wed Jan 23 06:01:57 2013
Thread 1 advanced to log sequence 2323 (LGWR switch)
Current log# 2 seq# 2323 mem# 0: /data03/oracle/oradata/UDSRED/redo02.rdo
Wed Jan 23 06:01:57 2013
Wed Jan 23 06:01:57 2013
Logminer Bld: Lockdown Complete. DB_TXN_SCN is 2548 1551493736
Wed Jan 23 06:01:57 2013
LNS: Standby redo logfile selected for thread 1 sequence 2323 for destination LOG_ARCHIVE_DEST_2
Wed Jan 23 06:01:57 2013
LNS: Standby redo logfile selected for thread 1 sequence 2323 for destination LOG_ARCHIVE_DEST_3
Wed Jan 23 06:01:59 2013
ALTER SYSTEM ARCHIVE LOG
Wed Jan 23 06:01:59 2013
Thread 1 advanced to log sequence 2324 (LGWR switch)
Current log# 3 seq# 2324 mem# 0: /data03/oracle/oradata/UDSRED/redo03.rdo
Wed Jan 23 06:01:59 2013
LNS: Standby redo logfile selected for thread 1 sequence 2324 for destination LOG_ARCHIVE_DEST_3
Wed Jan 23 06:01:59 2013
LNS: Standby redo logfile selected for thread 1 sequence 2324 for destination LOG_ARCHIVE_DEST_2
Wed Jan 23 06:02:00 2013
Wed Jan 23 06:02:00 2013
Logminer Bld: Done
Edited by: Imran on Jan 23, 2013 2:10 PMImran,
The information from alert log file is not sufficient.
Can you log switch on primary and monitor whether it is archiving in standby or not.
and you can monitor the changes in "v$managed_standby"
Also check for the errors using "v$dataguard_status"
SQL> select error_cdoe, message, timestamp from v$dataguard_status where dest_id=<n>; -
EXPDP Error in Oracle 11.2.0.1.0
Hello Team,
I have a problem in executing expdp/impdp in oracle version 11.2.0.1.0. Following is the error output. Traditional exp/imp is working fine.
Note: command executed on Oracle Linux on VMware
[oracle1@rac1 test]$ expdp
Export: Release 11.2.0.1.0 - Production on Mon Aug 12 15:29:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-31626: job does not exist
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
ORA-06512: at "SYS.KUPV$FT", line 991
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
Regards,Hello DK2010,
=======================================================================================================
SQL> set lines 100
SQL> set pagesize 200
SQL> /
OWNER OBJECT_TYPE
OBJECT_NAME
OBJECT_ID STATUS
SYS PACKAGE
DBMS_INTERNAL_LOGSTDBY
5067 VALID
SYS PACKAGE BODY
DBMS_INTERNAL_LOGSTDBY
10780 INVALID
===================================================================================================
UTLRP.SQL output:
====================================================================================================
SQL> @utlrp.sql
TIMESTAMP
COMP_TIMESTAMP UTLRP_BGN 2013-08-12 16:03:24
DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC> objects in the database. Recompilation time is proportional to the
DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid
DOC> objects.
DOC>
DOC> Use the following queries to track recompilation progress:
DOC>
DOC> 1. Query returning the number of invalid objects remaining. This
DOC> number should decrease with time.
DOC> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC> 2. Query returning the number of objects compiled so far. This number
DOC> should increase with time.
DOC> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC> This script automatically chooses serial or parallel recompilation
DOC> based on the number of CPUs available (parameter cpu_count) multiplied
DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC> On RAC, this number is added across all RAC nodes.
DOC>
DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC> recompilation. Jobs are created without instance affinity so that they
DOC> can migrate across RAC nodes. Use the following queries to verify
DOC> whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC> 1. Query showing jobs created by UTL_RECOMP
DOC> SELECT job_name FROM dba_scheduler_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC> 2. Query showing UTL_RECOMP jobs that are running
DOC> SELECT job_name FROM dba_scheduler_running_jobs
DOC> WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
DECLARE
ERROR at line 1:
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
ORA-06512: at "SYS.UTL_RECOMP", line 781
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
ORA-06512: at line 4
TIMESTAMP
COMP_TIMESTAMP UTLRP_END 2013-08-12 16:03:25
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
13
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
0
PL/SQL procedure successfully completed.
SQL> SELECT owner, object_type, object_name, object_id, status FROM SYS.dba_objects where object_name = 'DBMS_INTERNAL_LOGSTDBY';
OWNER OBJECT_TYPE
OBJECT_NAME
OBJECT_ID STATUS
SYS PACKAGE
DBMS_INTERNAL_LOGSTDBY
5067 VALID
SYS PACKAGE BODY
DBMS_INTERNAL_LOGSTDBY
10780 INVALID
==================================================
SELECT owner,object_type,object_name,status FROM dba_objects WHERE status = 'INVALID' ORDER BY owner, object_type, object_name;SQL> SQL>
OWNER OBJECT_TYPE OBJECT_NAME STATUS
DBSNMP PACKAGE BSLN INVALID
DBSNMP PACKAGE BSLN_INTERNAL INVALID
DBSNMP PACKAGE BODY BSLN INVALID
DBSNMP PACKAGE BODY BSLN_INTERNAL INVALID
DBSNMP SYNONYM MGMT_BSLN INVALID
PUBLIC SYNONYM DBA_LOGSTDBY_LOG INVALID
PUBLIC SYNONYM DBMS_ADVISOR INVALID
PUBLIC SYNONYM DBMS_SQLPA INVALID
PUBLIC SYNONYM DBMS_SQLTUNE INVALID
SYS FUNCTION LOGSTDBY$TABF INVALID
SYS FUNCTION LOGSTDBY$UTABF INVALID
SYS PACKAGE DBMS_ADVISOR INVALID
SYS PACKAGE DBMS_SQLDIAG_INTERNAL INVALID
SYS PACKAGE DBMS_SQLPA INVALID
SYS PACKAGE DBMS_SQLTUNE INVALID
SYS PACKAGE DBMS_SQLTUNE_INTERNAL INVALID
SYS PACKAGE PRVT_ADVISOR INVALID
SYS PACKAGE BODY AS_REPLAY INVALID
SYS PACKAGE BODY DBMS_ADDM INVALID
SYS PACKAGE BODY DBMS_ADVISOR INVALID
SYS PACKAGE BODY DBMS_APPLY_ERROR INVALID
SYS PACKAGE BODY DBMS_ARCH_PROVIDER_INTL INVALID
SYS PACKAGE BODY DBMS_ASH_INTERNAL INVALID
SYS PACKAGE BODY DBMS_AUTOTASK_PRVT INVALID
SYS PACKAGE BODY DBMS_AUTO_TASK_EXPORT INVALID
SYS PACKAGE BODY DBMS_CAPTURE_SWITCH_ADM INVALID
SYS PACKAGE BODY DBMS_CAPTURE_SWITCH_INTERNAL INVALID
SYS PACKAGE BODY DBMS_COMPRESSION INVALID
SYS PACKAGE BODY DBMS_DBFS_CONTENT_ADMIN INVALID
SYS PACKAGE BODY DBMS_DBFS_HS INVALID
SYS PACKAGE BODY DBMS_FEATURE_USAGE INVALID
SYS PACKAGE BODY DBMS_FEATURE_USAGE_INTERNAL INVALID
SYS PACKAGE BODY DBMS_INTERNAL_LOGSTDBY INVALID
SYS PACKAGE BODY DBMS_ISCHED INVALID
SYS PACKAGE BODY DBMS_LOGREP_EXP INVALID
SYS PACKAGE BODY DBMS_LOGSTDBY INVALID
SYS PACKAGE BODY DBMS_MANAGEMENT_PACKS INVALID
SYS PACKAGE BODY DBMS_PROPAGATION_INTERNAL INVALID
SYS PACKAGE BODY DBMS_REPORT INVALID
SYS PACKAGE BODY DBMS_SERVER_ALERT INVALID
SYS PACKAGE BODY DBMS_SERVER_ALERT_PRVT INVALID
SYS PACKAGE BODY DBMS_SMB INVALID
SYS PACKAGE BODY DBMS_SMB_INTERNAL INVALID
SYS PACKAGE BODY DBMS_SPACE INVALID
SYS PACKAGE BODY DBMS_SPM INVALID
SYS PACKAGE BODY DBMS_SPM_INTERNAL INVALID
SYS PACKAGE BODY DBMS_SQLDIAG INVALID
SYS PACKAGE BODY DBMS_SQLDIAG_INTERNAL INVALID
SYS PACKAGE BODY DBMS_SQLPA INVALID
SYS PACKAGE BODY DBMS_SQLTCB_INTERNAL INVALID
SYS PACKAGE BODY DBMS_SQLTUNE INVALID
SYS PACKAGE BODY DBMS_SQLTUNE_INTERNAL INVALID
SYS PACKAGE BODY DBMS_SQLTUNE_UTIL1 INVALID
SYS PACKAGE BODY DBMS_SQLTUNE_UTIL2 INVALID
SYS PACKAGE BODY DBMS_STATS INVALID
SYS PACKAGE BODY DBMS_STATS_INTERNAL INVALID
SYS PACKAGE BODY DBMS_STREAMS_ADM INVALID
SYS PACKAGE BODY DBMS_STREAMS_ADM_UTL INVALID
SYS PACKAGE BODY DBMS_STREAMS_AUTO_INT INVALID
SYS PACKAGE BODY DBMS_STREAMS_SM INVALID
SYS PACKAGE BODY DBMS_SWRF_INTERNAL INVALID
SYS PACKAGE BODY DBMS_SWRF_REPORT_INTERNAL INVALID
SYS PACKAGE BODY DBMS_UNDO_ADV INVALID
SYS PACKAGE BODY DBMS_WORKLOAD_CAPTURE INVALID
SYS PACKAGE BODY DBMS_WORKLOAD_REPLAY INVALID
SYS PACKAGE BODY DBMS_WORKLOAD_REPOSITORY INVALID
SYS PACKAGE BODY DBMS_WRR_INTERNAL INVALID
SYS PACKAGE BODY DBMS_XPLAN INVALID
SYS PACKAGE BODY HM_SQLTK_INTERNAL INVALID
SYS PACKAGE BODY LOGMNR_DICT_CACHE INVALID
SYS PACKAGE BODY PRVT_ACCESS_ADVISOR INVALID
SYS PACKAGE BODY PRVT_ADVISOR INVALID
SYS PACKAGE BODY PRVT_COMPRESSION INVALID
SYS PACKAGE BODY PRVT_HDM INVALID
SYS PACKAGE BODY PRVT_PARTREC_NOPRIV INVALID
SYS PACKAGE BODY PRVT_REPORT_TAGS INVALID
SYS PACKAGE BODY PRVT_SQLADV_INFRA INVALID
SYS PACKAGE BODY PRVT_SQLPA INVALID
SYS PACKAGE BODY PRVT_SQLPROF_INFRA INVALID
SYS PACKAGE BODY PRVT_SQLSET_INFRA INVALID
SYS PACKAGE BODY PRVT_SYS_TUNE_MVIEW INVALID
SYS PACKAGE BODY PRVT_TUNE_MVIEW INVALID
SYS PACKAGE BODY PRVT_WORKLOAD INVALID
SYS PACKAGE BODY PRVT_WORKLOAD_NOPRIV INVALID
SYS PROCEDURE DBMS_FEATURE_AUM INVALID
SYS PROCEDURE DBMS_FEATURE_AUTOSTA INVALID
SYS PROCEDURE DBMS_FEATURE_AWR INVALID
SYS PROCEDURE DBMS_FEATURE_REGISTER_ALLFEAT INVALID
SYS PROCEDURE DBMS_FEATURE_SEGADV_USER INVALID
SYS PROCEDURE DBMS_FEATURE_UTILITIES1 INVALID
SYS PROCEDURE DBMS_FEATURE_UTILITIES2 INVALID
SYS PROCEDURE DBMS_FEATURE_UTILITIES3 INVALID
SYS PROCEDURE DBMS_FEATURE_UTILITIES4 INVALID
SYS PROCEDURE DBMS_FEATURE_WCR_CAPTURE INVALID
SYS PROCEDURE DBMS_FEATURE_WCR_REPLAY INVALID
SYS PROCEDURE LOGMNR_KRVRDA_TEST_APPLY INVALID
SYS TYPE SCHEDULER$_REMOTE_ARG INVALID
SYS TYPE SCHEDULER$_REMOTE_ARG_LIST INVALID
SYS TYPE SCHEDULER$_REMOTE_DB_JOB_INFO INVALID
SYS TYPE BODY WRI$_ADV_ABSTRACT_T INVALID
SYS TYPE BODY WRI$_ADV_COMPRESSION_T INVALID
SYS TYPE BODY WRI$_ADV_HDM_T INVALID
SYS TYPE BODY WRI$_ADV_OBJSPACE_TREND_T INVALID
SYS TYPE BODY WRI$_ADV_SQLACCESS_ADV INVALID
SYS TYPE BODY WRI$_ADV_SQLTUNE INVALID
SYS TYPE BODY WRI$_ADV_TUNEMVIEW_ADV INVALID
SYS TYPE BODY WRI$_REPT_PLAN_DIFF INVALID
SYS TYPE BODY WRI$_REPT_SQLMONITOR INVALID
SYS TYPE BODY WRI$_REPT_SQLPI INVALID
SYS TYPE BODY WRI$_REPT_SQLT INVALID
SYS VIEW AQ$AQ_PROP_TABLE_R INVALID
SYS VIEW AQ$SCHEDULER$_EVENT_QTAB_R INVALID
SYS VIEW AQ$SCHEDULER$_REMDB_JOBQTAB INVALID
SYS VIEW AQ$SCHEDULER$_REMDB_JOBQTAB_R INVALID
SYS VIEW AQ$SCHEDULER_FILEWATCHER_QT_R INVALID
SYS VIEW AQ$_AQ$_MEM_MC_F INVALID
SYS VIEW AQ$_AQ_PROP_TABLE_F INVALID
SYS VIEW AQ$_SCHEDULER$_EVENT_QTAB_F INVALID
SYS VIEW AQ$_SCHEDULER$_REMDB_JOBQTAB_F INVALID
SYS VIEW AQ$_SCHEDULER_FILEWATCHER_QT_F INVALID
SYS VIEW DBA_LOGSTDBY_LOG INVALID
121 rows selected.
=================================================================================================================
How do i fix this invalid sys objects.
Regards, -
Hi
My Oracle version is , oracle 9i , i wanted to import a dump file which has taken by same version of oracle.when i executed the imp command for that dump file , i'm getting following error message.
Export file created by EXPORT:V09.02.00 via conventional path
import done in UTF8 character set and UTF8 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses US7ASCII character set (possible charset conversion)
export server uses AL16UTF16 NCHAR character set (possible ncharset conversion)
IMP-00017: following statement failed with ORACLE error 4068:
"BEGIN "
"sys.dbms_logrep_imp.instantiate_schema(schema_name=>'Hotels', export_db_na"
"me=>'Hotels.US.ORACLE.COM', inst_scn=>'1363425837');"
"COMMIT; END;"
IMP-00003: ORACLE error 4068 encountered
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "SYS.DBMS_LOGREP_UTIL" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "SYS.DBMS_LOGREP_IMP", line 271
How can i solve this ? can some body help me plz ?
Thank you
Luke
Edited by: user2975888 on Jul 10, 2009 7:36 AMHi
Sorry for delayed reply with results.
SQL> select count(*) from dba_objects where status like '%INVALID%';
COUNT(*)
29
OWNER OBJECT_NAME OBJECT_TYPE
SYS DBA_LOGSTDBY_LOG VIEW
SYS DBA_LOGSTDBY_PROGRESS VIEW
SYS DBMS_ASYNCRPC_PUSH PACKAGE BODY
SYS DBMS_CAPTURE_ADM_INTERNAL PACKAGE BODY
SYS DBMS_CAPTURE_PROCESS PACKAGE BODY
SYS DBMS_DEFER_QUERY PACKAGE BODY
SYS DBMS_DEFER_SYS PACKAGE BODY
SYS DBMS_DEFER_SYS_PART1 PACKAGE BODY
SYS DBMS_INTERNAL_LOGSTDBY PACKAGE BODY
SYS DBMS_LOGMNR_D PACKAGE BODY
SYS DBMS_LOGMNR_FFVTOLOGMNRT PROCEDURE
SYS DBMS_LOGMNR_INTERNAL PACKAGE BODY
SYS DBMS_LOGMNR_LOGREP_DICT PACKAGE BODY
SYS DBMS_LOGMNR_OCTOLOGMNRT PROCEDURE
SYS DBMS_LOGMNR_SESSION PACKAGE BODY
SYS DBMS_LOGREP_UTIL PACKAGE BODY
SYS DBMS_LOGSTDBY PACKAGE BODY
SYS DBMS_REPCAT_MAS PACKAGE BODY
SYS DBMS_REPCAT_SNA_UTL PACKAGE BODY
SYS DBMS_REPCAT_UTL PACKAGE BODY
SYS DBMS_SNAPSHOT PACKAGE BODY
SYS DBMS_STREAMS_ADM_UTL PACKAGE BODY
SYS LOGMNR_DICT_CACHE PACKAGE BODY
SYS LOGMNR_GTLO3 PROCEDURE
SYS LOGMNR_KRVRDA_TEST_APPLY PROCEDURE
SYS LOGMNR_KRVRDLUID3 PROCEDURE
SYS LOGMNR_KRVRDREPDICT3 PROCEDURE
GATEWAY AB_TRIGGER TRIGGER
GATEWAY APPLETINFO_TRIGGER TRIGGER
29 rows selected
This is the error i'm getting when i'm importing the dmp file .
Import: Release 9.2.0.7.0 - Production on Sat Jul 11 18:48:37 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning option
JServer Release 9.2.0.7.0 - Production
Export file created by EXPORT:V09.02.00 via conventional path
import done in UTF8 character set and UTF8 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses US7ASCII character set (possible charset conversion)
export server uses AL16UTF16 NCHAR character set (possible ncharset conversion)
IMP-00017: following statement failed with ORACLE error 4068:
"BEGIN "
"sys.dbms_logrep_imp.instantiate_schema(schema_name=>'GATEWAY', export_db_na"
"me=>'GATEWAY.US.ORACLE.COM', inst_scn=>'1363425837');"
"COMMIT; END;"
IMP-00003: ORACLE error 4068 encountered
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "SYS.DBMS_LOGREP_UTIL" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "SYS.DBMS_LOGREP_IMP", line 271
ORA-06512: at line 2
Thanks
Luke -
DBMS_LOGSTDBY.SKIP_ERROR doesn't work
Hi guru's,
I have e a 11.2.0.3 sql-apply dataguard running (prd1 > prd2) and I want to skip grants and revokes on the scott schema.I have done the following (based on the (http://oracledocs.shu.ac.uk/oracle/B28359_01/appdev.111/b28419/d_lsbydb.htm#i997288 document)
ALTER DATABASE STOP LOGICAL STANDBY APPLY;
CREATE OR REPLACE PROCEDURE OSCAR (
old_stmt IN VARCHAR2,
stmt_type IN VARCHAR2,
schema IN VARCHAR2,
name IN VARCHAR2,
xidusn IN NUMBER,
xidslt IN NUMBER,
xidsqn IN NUMBER,
error IN VARCHAR2,
new_stmt OUT VARCHAR2
) AS
BEGIN
-- Default to what we already have
new_stmt := old_stmt;
-- Ignore any GRANT errors on SYS or HR schemas
IF INSTR(UPPER(old_stmt),'GRANT') > 0
AND UPPER(schema) = 'SCOTT'
THEN
new_stmt := NULL;
END IF;
END oscar;
EXECUTE DBMS_LOGSTDBY.SKIP_ERROR ( stmt => 'NON_SCHEMA_DDL',schema_name => NULL, object_name => NULL, proc_name => 'SYS.OSCAR')
--EXECUTE DBMS_LOGSTDBY.UNSKIP_ERROR ( stmt => 'NON_SCHEMA_DDL')
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
But still grants like grant select on scott.emp to dbsnmp is applyed on the prd2 database?
So what I am donign wrong ?
thanks for any help.
regards oScarHi I correct you procedure;
SQL> CREATE OR REPLACE PROCEDURE OSCAR(
2 old_stmt IN VARCHAR2,
3 stmt_type IN VARCHAR2,
4 schema IN VARCHAR2,
5 name IN VARCHAR2,
6 xidusn IN NUMBER,
7 xidslt IN NUMBER,
8 xidsqn IN NUMBER,
9 error IN VARCHAR2,
10 new_stmt OUT VARCHAR2) AS
11
12 BEGIN
13 -- Default to what we already have
14 new_stmt := old_stmt;
15
16 -- Ignore any GRANT errors on SYS or SCOTT schemas
17 IF INSTR(UPPER(old_stmt),'GRANT') > 0
18 THEN
19 IF schema IS NULL
20 OR (schema IS NOT NULL AND (UPPER(schema) = 'SYS'
21 OR UPPER(schema) = 'SCOTT'))
22 THEN
23 new_stmt := NULL;
24 -- record the fact that an error was skipped
25 NULL;
26 END IF;
27 END IF;
28 END OSCAR;
29 /
Procedure created.
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> EXECUTE DBMS_LOGSTDBY.SKIP_ERROR ( stmt => 'NON_SCHEMA_DDL',schema_name => NULL, object_name => NULL, proc_name =>
'SYS.OSCAR')
PL/SQL procedure successfully completed.
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Database altered.
I have test it but it still doesn't work. -
DBMS_LOGSTDBY.BUILD Seems to Hang
Hi Group,
One step on the logical standby creation is to execute the package DBMS_LOGSTDBY.BUILD, however it has been executing for almost three days and it does not return the sql promt, I read about metalink note 747495.1 DBMS_LOGSTDBY.BUILD Seems to Hang And Does Not Return To SQL prompt which says that package waits for all transactions to finish, so I restart the primary database in restrict mode, so anybody can connect, and execute DBMS_LOGSTDBY.BUILD again during this weekend. The same result, it didn't finish execution.
Any idea about what it could be.
Thanks a lot.Imran,
The information from alert log file is not sufficient.
Can you log switch on primary and monitor whether it is archiving in standby or not.
and you can monitor the changes in "v$managed_standby"
Also check for the errors using "v$dataguard_status"
SQL> select error_cdoe, message, timestamp from v$dataguard_status where dest_id=<n>; -
ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner
Hi, has anyone ever got this error in 11.2.0.3 primary database while trying to convert a physical standby to a logical standby?
ThanksPer the documentation:
4.2 Step-by-Step Instructions for Creating a Logical Standby Database
Creating a Logical Standby Database
4.2.2 Stop Redo Apply on the Physical Standby Database
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
4.2.3.1 Prepare the Primary Database for Role Transitions
Has you adjust primary database init.ora parameters to be prepared for switchovers.
4.2.3.2 Build a Dictionary in the Redo Data
SQL> EXECUTE DBMS_LOGSTDBY.BUILD;
this puts a Multi-vertion Data Dictionary (MVDD) is the archive logs that are sent to the standby.
This is what fails with:
SQL> exec dbms_logstdby.build ;
BEGIN dbms_logstdby.build ; END;
ERROR at line 1:
ORA-01339: LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary
ORA-06512: at "SYS.DBMS_LOGMNR_INTERNAL", line 5972
ORA-06512: at "SYS.DBMS_LOGMNR_INTERNAL", line 6070
ORA-06512: at line 1
4.2.4.1 Convert to a Logical Standby Database
SQL> SHUTDOWN ABORT;
SQL> STARTUP MOUNT EXCLUSIVE;
SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY db_name;
this consumes the data dictionary into the standby for convertion. It is used by SQL apply to understandby object id's because the standby does not know the names of the objects that are in the primary database.
then you add some logical standby parameters and open the database and start SQL apply.
SQL> ALTER DATABASE OPEN RESETLOGS;
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
So running EXECUTE DBMS_LOGSTDBY.BUILD; is a standby alone process that can be tested any time. It does nothing to the primary except extract dictionary information and puts it in the archive logs.
I find no information on DBMS_LOGSTDBY.BUILD; ever failing. It must be specific to this primary database.
Thanks -
Hi All,
I am getting the following errors when I am trying to connect with datapump.My db is 10g and os is linux.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
ORA-31626: job does not exist
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "SYS.DBMS_LOGSTDBY", line 24
ORA-06512: at "SYS.KUPV$FT", line 676
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called
When I tried to compile this package I am getting the following error
SQL> alter package DBMS_INTERNAL_LOGSTDBY compile body;
Warning: Package Body altered with compilation errors.
SQL> show error
Errors for PACKAGE BODY DBMS_INTERNAL_LOGSTDBY:
LINE/COL ERROR
1405/4 PL/SQL: SQL Statement ignored
1412/38 PL/SQL: ORA-00904: "SQLTEXT": invalid identifier
1486/4 PL/SQL: SQL Statement ignored
1564/7 PL/SQL: ORA-00904: "DBID": invalid identifier
1751/2 PL/SQL: SQL Statement ignored
1870/7 PL/SQL: ORA-00904: "DBID": invalid identifier
Can anyony suggest/guide me how to resolve the issue.
Thanks in advanceSQL> SELECT OBJECT_TYPE,OBJECT_NAME FROM DBA_OBJECTS
2 WHERE OWNER='SYS' AND STATUS<>'VALID';
OBJECT_TYPE OBJECT_NAME
VIEW DBA_COMMON_AUDIT_TRAIL
PACKAGE BODY DBMS_INTERNAL_LOGSTDBY
PACKAGE BODY DBMS_REGISTRY_SYS
Thanks -
Error in starting Adobe Bridge in Photoshop CS2
I've just installed Photoshop CS2, however upon opening Adobe Bridge this error message appears " The application has failed to start because libagluc28.dll was not found. Reinstalling to application may fix the problem"
I have reinstalled and click repair but to no avail
I followed Adobe Support Knowledgebase solution and run CMD and this appears:
c:Documents and Settings/Jesus M Ferraris>
then i entered the command
cacls c:\windows\installer /T /E /C /G administrators:F
but an error message appears - 'cacls' is not recognized as an internal or external command, operable program or bathc file
I also entered the next command
cacls "c:\documents and setting\all users" /Y /E /C /G administrators:F
still the same error as above appears, Please help, have I miss something or was my procedure correct...
P4, 512ram, WXP 80gHDVery useful.
Good Luck.
My
Si
tes
Maybe you are looking for
-
I updated my Iphone5S to IOS 7.1.2 and some contacts disappeared from my phone. I use over the air sync wtih Exchange Server account, and any change in the contacts list from outlook isn't being reflected on my phone.Why is this happening and what ca
-
With the problems experienced with Itunes 7.7 - can I use Time Machine and restore the pre upgraded version? If so do I just find it and click restore? Any help appreciated.
-
BufferedImage with Non-GUI OS?!!!
I have a Servlet that creates a BufferedImage instance and then writes the Image as "image/png" mime type using the javax.imageio.ImageIO. When I deploy the Servlet I got an exception: 500 Servlet Exception java.lang.NoClassDefFoundError at test
-
Every time i try to log in i keep getting logged out and so on n a loop ?
Please help after I had a software update I can't log back in unless I use the safe mode . Every time I log in i get the blue screen and then back to the log in screen . Any advise . I do not want to do another install and lose all my stuff .
-
Problem to import my file swf in my librairy
Hi, I have a probleme. I am using flash cs5 and I created a file called : animation.swf (his weight is 880 ko) My goal is to create a loading barr for my file (animation.swf) but when I want to import my file animation.swf in my library it doesn t wo