Wrc Generates ORA-15557?
Jul 27, 2010
I just completed a capture and I am trying to calibrate the workload but I get this error and I have not info about it.
I chmod the dir to 777 (just to make sure it wasn't permission) My sid is set to the correct db. Oracle_home, etc are set.
wrc MODE=calibrate REPLAYDIR=.
Workload Replay Client: Release 11.2.0.1.0 - Production on Tue Jul 27 14:59:33 2010
Copyright © 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Errors in file :
ORA-15557: workload replay client cannot access the replay directory or the database version do not match the preprocessing one
View 3 Replies
Feb 17, 2012
This generates a CSV file in an directory. When it runs for the 1st time it take SYSDATE -7 data. After the 1st run it appends the data since the last run. Now my problem is the appending happens at the bottom of the file and every time the header appears. I want the header only the first time and the new data should keep appending at the top so that i get the latest data always at the top.
View 18 Replies
View Related
Jan 31, 2013
I'm looking for errors in alert.log, I thought that every "ORA-XX" would be a incident in adrci, but "i have missed" some ORAS-XX
I have a wrong job in my test environment which generates an ORA-12012 every 5 minutes. If we chech the alert.log trace we can see that there is a recor every five minutes (more of less)
oooo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo
adrci> show alert -tail 2
2013-01-31 12:59:01.901000 +01:00
SMCO started with pid=23, OS id=20719
2013-01-31 13:00:23.033000 +01:00
Errors in file /u01/app/oracle/diag/rdbms/xe/XE/trace/XE_j000_20765.trc:
ORA-12012: error on auto execute of job "TEST"."WRONG_JOB"
ORA-04063: package body ""TEST"."WRONG_JOB"" has errors
ORA-06508: PL/SQL: could not find program unit being called: ""TEST"."WRONG_JOB""
[code].....
But, if we look for for incidents
oooo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo--oo
adrci> show incidents
ADR Home = /opt/oracle/diag/rdbms/xe/XE:
*************************************************************************
INCIDENT_ID PROBLEM_KEY CREATE_TIME
-------------------- ----------------------------------------------------------- ----------------------------------------
23393 ORA 600 [kzsviver:1] 2012-09-27 09:19:55.054000 +02:00
23394 ORA 600 [kzsviver:1] 2012-09-27 09:20:13.540000 +02:00
23409 ORA 600 [kzsviver:1] 2012-09-27 09:56:35.688000 +02:00
[code].....
This ORA-12012 doesn't appears.
View 8 Replies
View Related
Dec 7, 2011
Whenever any transaction happen in database redo has generated for this transaction. Do select statement treat as a transaction as it doesn't modify any thing in database. And If select statement should not be a transaction, there should not be any redo generation for select statement.
So is select statement generate redo? If yes then Why ?
View 1 Replies
View Related
Jul 24, 2013
I am trying the new Oracle 12c and its feature to create columns with the keyword IDENTITY. I create a table CREATE TABLE xt (a NUMBER GENERATED by default AS IDENTITY PRIMARY KEY, b VARCHAR2(10));
And populate it, sometimes specifying the value for a and sometimes relying on the system to generate the value:
INSERT INTO xt (b) values ('a');INSERT INTO xt (b, a) values ('b', default);INSERT INTO xt (b, a) values ('c', 3);INSERT INTO xt (b) values ('d');INSERT INTO xt (b) values ('e');
The problem is that the fourth INSERT fails because the system tries to use the value 3 which is already taken. The fifth statement gets the value 4.
And the table now contains: A B - -1 a 2 b 3 c 4 e Is there something I am missing? I understood that by specifying BY DEFAULT, I would be allowed to sometimes specify values on my own without them interfering with the generated values. I now that the same thing works correctly in MySQL (where I would get five rows from 1 to 5 with the same INSERT statements) /nikos
View 11 Replies
View Related
Aug 9, 2011
Calling function
select PACK.MAIN('blah') from dual
generates:
ORA-14551: cannot perform a DML operation inside a query
ORA-06512: at "SYSADM.NEW_QUANTUM_PACK", line 756
ORA-06512: at "SYSADM.NEW_QUANTUM_PACK", line 245
Unfortunately the Body is not accessible to see.The spec of the function is:
FUNCTION MAIN (mvar IN varchar2) RETURN varchar2; I read somewhere that I can call it like:
var myVar VARCHAR2; call PACK.MAIN('blah') into :myVar
But this generates: ORA-01008: not all variables bound
View 3 Replies
View Related
Nov 11, 2011
I set 'maxopenfiles 4' when allocating channel to sbt in my products env, I got 2 backup pieces in one backup set because that tablespace has 7 datafiles. Other configuration is kept as default, such as no maxsize, no MAXPIECESIZE, and etc setting.
I read document from Oracle. It says:"By default a backup set contains one backup piece. To restrict the size of each backup piece, specify the MAXPIECESIZE option of the CONFIGURE CHANNEL or ALLOCATE CHANNEL commands. " And also, maxopenfiles configure does not force another backup piece generated. So, why do I get another backup piece?
BTW, I tried this on another testing environment. I only get one backup piece even there are more than 2 times maxopnefiles datafiles.
View 7 Replies
View Related
