ORA-28137: Invalid FGA audit Handler

I have an Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit running on AIX
I am being hit with the following error when querying a table :
SELECT * FROM ADM.TABLE_A;
ORA-28137: Invalid FGA audit Handler
select * from DBA_AUDIT_POLICIES gives me 9 tables in the ADM schema that we have auditing turned on. Selecting from any of those 9 tables being audited produces the above error. I looked in metalink oracle support but it has no mention of this error in the knowledge base. This forum has no earlier mention of this error too. Documentation wasn't helpful either. Hence just checking if anybody has any information on this error.

PF_FUNCTION column in the DBA_AUDIT_POLICIES view had a non-existent function causing the statement failure

Similar Messages

OCCI Error - ORA-32102: invalid OCI handle

Hi,
I'm completely new to OCCI and Linux and trying to run the simple OCCI program given in oracle site (http://www.oracle.com/technology/tech/oci/occi/occibasic.html) to connect a remote Oracle DB server.
#include <iostream>
#include <occi.h>
using namespace std;
using namespace oracle::occi;
int main()
Environment* env = Environment::createEnvironment();
Connection* conn = env->createConnection("testdb", "testdb", "192.168.10.118:1521/ORADB"); // user, password, url
Statement* stmt = conn->createStatement();
stmt->setSQL("INSERT into FRUITS (fruit, amt) VALUES ('apple', 10)");
stmt->executeUpdate();
conn->terminateStatement(stmt);
env->terminateConnection(conn);
Environment::terminateEnvironment(env);
return 0;
When I try to run it after compilation it gives the following error.
ORA-32102: invalid OCI handle
The error should be in the line: Connection* conn = env->createConnection("testdb", "testdb", "192.168.10.118:1521/ORADB");
I could track it by placing a cout<< there.
Why this is and how can I handle this error? Please post your experience.
Thanks

Hi,
I found the reason. It may due to the permission level of the user "testdb". When I tried with a different user it worked!
Thanks

ORA-31001:Invalid resource handle or path name"/apps/batchadm/files/test.xm

Hi,
When i am trying to parse the xml document using XDB API. I passed the XML file path to the parse function and making use of that at below lines of code.
xmlparser.setBaseDir(prsr, dir);
xmlparser.parse (prsr, dir || '/' || file_in);
In thsi sceneraio it is giving the below error saying invalid path. But i am giving the right path. And even the file having all permission( 777).
Can any please help me why i am getting this error even if i mentioned the correct path? Is there anything related the permission grants?
ORA-31001: Invalid resource handle or path name "/apps/batchadm/files/test.xml"
ORA-06512: at "SYS.XDBURITYPE", line 11
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 142
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-06512: at "XDB.DBMS_XMLPARSER", line 119
ORA-06512: at "SIGCAP.PARSE_DOCUMENT", line 11
Thanks,
shashi

Could be privs on OS or database level. Check and see what happens if grant yourself the DBA role. Check if the database software owner (ps -ef | grep pmon) is allowed to write in that directory and/or create a file in that directory. Does the OS make use of ACL's (and/or is, for instance Secure, Linux used)....?

FTP-ing to XE: ORA-31001: Invalid resource handle or path name

Hi guys,
Hope you can help me out here. I get a very confusing message during trying to FTP a directory to the /i/ files in XE. The connectiopn works just fine, but when I try to send something to the folder I get the following message:
ORA-31001: Invalid resource handle or path name "/i/themes/eServices"
Any thoughts? Thanks!

I haven't checked the docs, but it does remind me of the PL/SQL steps required to do similar things. Maybe you need to mkdir first (could it be XMKD? See below...)
C:\>ftp
ftp> open localhost 2100
Connected to XYZHOST.mycompany.com.
220- XYZHOST
Unauthorised use of this FTP server is prohibited and may be subject to civil an
d criminal prosecution.
220 XYZHOST FTP Server (Oracle XML DB/Oracle Database) ready.
User (XYZHOST.mycompany.com:(none)): sys
331 pass required for SYS
Password:
230 SYS logged in
ftp> pwd
257 "/" is current directory.
ftp> cd i
250 CWD Command successful
ftp> pwd
257 "/i" is current directory.
ftp> quote help
214- The following commands are recognized:
USER PORT RETR MSND* ALLO* DELE SITE* MKD XPWD
PASS PASV STOR MSOM* REST* CWD SYST XMKD CDUP
ACCT* TYPE APPE MSAM* RNFR XCWD STAT* RMD XCUP*
REIN* STRU MLFL* MRSQ* RNTO LIST HELP XRMD STOU
QUIT MODE MAIL* MRCP* ABOR NLST NOOP PWD
214 (*'s => unimplemented)
ftp>

XML Basic Demo - ORA-31001: Invalid resource handle or path name

I have been attempting to install the xml basic demo into Oracle 9.2.0.3. The initial setup appears to go OK, but upon attempting to run '1.1 Make Directories' as the demo user (in my case: xdbdemouser/xdbdemouser), I get the following error message:
ERROR at line 1:
ORA-31001: Invalid resource handle or path name "/home/XDBDEMOUSER/"
ORA-06512: at "XDB.DBMS_XDB", line 168
ORA-06512: at line 5
If I run this script as system or xdb, it appears to work OK. Obviously, the xdbdemouser exists in the database....
Can anyone help ??
thx - matt

Did you run 0.0 and 0.1 before running this step. You must run resetDemo before starting the demo for the first time.

ORA-31001: Invalid resource handle or path name

I am using Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production.
I need to read xml contents from a file at D:\ on my windows system.
File name is test.xml.
I am using the system account as its a personal server.
I tried as follows:
SQL> CREATE DIRECTORY myxml AS 'D:';
SQL> declare
2 parser xmlparser.Parser;
3 begin
4 xmlparser.parse(parser,'myxml\test.xml');
5 end;
6 /
declare
ERROR at line 1:
ORA-31001: Invalid resource handle or path name "myxml\test.xml"
ORA-06512: at "SYS.XDBURITYPE", line 11
ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 142
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-29280: invalid directory path
ORA-06512: at "XDB.DBMS_XMLPARSER", line 120
ORA-06512: at line 4
D: is a FAT32 partition so Windows 7 offers no acl/permission restrictions. I have also tried from other different locations and the error is the same.
Please help me.

907985 wrote:
SQL> CREATE DIRECTORY myxml AS 'D:';
ORA-29280: invalid directory path
ORA-06512: at "XDB.DBMS_XMLPARSER", line 120I haven't tried it, but perhaps it's as simple as error message implies. Try with at least one directory e.g. D:\ or D:\somefoldername in the directory object's path name.

Handle null value in char infoobject -data type DATE(ora-01722 invalid num)

Hi,
We have a DSO with a info object in the Data fields. The char info object has the data type DATE and most often it has the null value. but some times it has data in it.
When ever we were trying to run a report on the DSO it throws a error as ORA- 01722 INVALID NUMBER.
we tried editing PSA data and placing 00000000 for null values - and had a message invalid date.
suggestions pls
Regards.

Hello,
Please check the note given below
https://service.sap.com/sap/support/notes/1327167.
If null value is the problem, change the query setting for not to show the null values. Just add a filter in ZDAT to exclude "NULL"
Thanks
Nidhi

"ORA-00903: invalid table name" when enqueue using a CLOB in an ADT payload

I am attempting to enqueue into an AQ that has an ADT with a CLOB field in it. If I leave the CLOB empty, it works. As soon as I place content in it, I get the error below in the BPEL log.
I actually get the same problem when I run the "AQ_ADT_with_CLOB_Payload" example. Please help!
Error in the BPEL log:
<2005-11-08 09:22:07,784> <ERROR> <default.collaxa.cube.ws> <AQ Adapter::Outbound> MessageWriter_enqueue: Could not enqueue message due to database error
<2005-11-08 09:22:07,784> <ERROR> <default.collaxa.cube.ws> <AQ Adapter::Outbound>
java.sql.SQLException: ORA-00903: invalid table name
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_describe(T4CPreparedStatement.java:661)
at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:951)
at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:693)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1057)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2901)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2942)
at oracle.tip.adapter.aq.database.MessageWriter.doEnqueue(MessageWriter.java:530)
at oracle.tip.adapter.aq.database.MessageWriter.enqueue(MessageWriter.java:341)
at oracle.tip.adapter.aq.database.MessageWriter.writeMessage(MessageWriter.java:303)
at oracle.tip.adapter.aq.outbound.AQEnqueuer.execute(AQEnqueuer.java:108)
at oracle.tip.adapter.aq.AQInteraction.executeRunTime(AQInteraction.java:194)
at oracle.tip.adapter.aq.AQInteraction.execute(AQInteraction.java:180)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:469)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:652)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:441)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:310)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:184)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:316)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:185)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3398)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1905)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:100)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:185)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5410)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1300)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:509)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:307)
at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:76)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:748)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:921)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)

OK, I figured it out myself. :)
Turns out when I define the queue name in the AQ Adapter definition, I was specifying "<Default Schema>" as the schema name. When I changed this to my actual schema name (eg: "SCOTT"), it worked. Nice little bug there!
The reason it broke with the example program is because I was changing the schema name before I deployed it. As I didn't have a SCOTT schema.
So the moral of the story here is, don't use "<Default Schema>"!
I was running on 10.1.2.0.0 [build #1787 ]. In case anyone wants to fix this.

ORA-01722: invalid number error coming in Oracle 10g.

Hi,
We are getting the error "ORA-01722: invalid number" while opening a cursor using CURSOR FOR LOOP.
This error has started coming only after we have migrated to Oracle 10g from Oracle 9i. Earlier the same code used to work properly. And also on Oracle 10g, its not happening every time. Sometimes it gives error while sometimes it works.
Does anybody know about any such bug in Oracle 10g. Our cursor is a parametrized cursor accepting a VARCHAR2 parameter and the value we are passing to it is also character.
Our database is Oracle 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production and is running on UNIX server.

And also on Oracle 10g, its not happening every time. Sometimes it gives error while sometimes it works. This is typically due to
a) environment settings that differ from session to session
b) or more often, data
The actual error means that Oracle expects a number and is unable to obtain a number from the input (data or SQL or bind variables) supplied. I agree with William that it looks a lot like an implicit TO_NUMBER() conversion failing.
Why not add a debug exception handler to the code? When that exception occurs, dump the PL/SQL call stack and values of all variables and parameters to a debug/logging table (using an autonomous transaction).

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

ORA-01017: invalid username/password; logon denied

Hello colleagues,
in TCode SM21 we've got a lot of following errors, that were repeated very often:
10:25:09 BTC 010                             BY 2 Database error 1017 at CON
10:25:09 BTC 010                             BY 0 > ORA-01017: invalid username/password; logon denied
10:25:09 BTC 010                             BY 2 Database error 1017 at CON
10:25:09 BTC 010                             BY 0 > ORA-01017: invalid username/password; logon denied
10:25:09 BTC 010                             R1 9 Initialization DB-Connect Failed, Return Code 000256
10:25:09 BTC 010                             Q0 2 Stop Workproc10, PID 3549
Background processes only affected and seems to be restarted after every attempt for connection into database.
After restart fo system (DB + ABAP) problem still persists, but does not occur that often. In productive system approximately once in every 2 hours, but is still there.
System environment:
DB: Oracle Release 10.2.0.2.0
OS: HP-UX
SAP: SAP ECC 6.0
Listener is up and running:
oraqxs   499     1 0 10:15:31 ?         0:01 /oracle/QXS/102_64/bin/tnslsnr LISTENER_QXS -inherit
R3trans working as well:
mucsx032:qxsadm 29> R3trans -d -v
This is R3trans version 6.14 (release 700 - 10.09.07 - 09:57:00).
R3trans finished (0000).
Below is extract from WP tracefile.
trc file: "dev_w10", trc level: 1, release: "700"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, MJ
M sysno      02
M sid        QXS
M systemid   274 (HP (IA-64) with HP-UX)
M relno      7000
M patchlevel 0
M patchno    133
M intno      20050900
M make:      single threaded, ASCII, 64 bit, optimized
M pid        3549
M
M
M Wed May 6 10:25:09 2009
M kernel runs with dp version 232(ext=109) (@(#) DPLIB-INT-VERSION-232)
M length of sys_adm_ext is 364 bytes
M ThInit: running on host ciqxs02
M calling db_connect ...
C Oracle Client Version: '10.2.0.1.0'
C Client NLS settings: AMERICAN_AMERICA.WE8DEC
C Logon as OPS$-user to get SAPDAT's password
C Connecting as /@QXS on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
C Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
C    0 WE8DEC                                                    1 600000000299f0a0 60000000029a6a20 60000000029aa408
C Attaching to DB Server QXS (con_hdl=0,svchp=60000000029aa338,srvhp=60000000029ac688)
C Starting user session (con_hdl=0,svchp=60000000029aa338,srvhp=60000000029ac688,usrhp=60000000029a7238)
C *** ERROR => OCI-call 'OCISessionBegin' failed with rc=1017
[dboci.c      4532]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c    11044]
C Try to connect with default password
C Connecting as SAPDAT/<pwd>@QXS on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
C Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
C    0 WE8DEC                                                    1 600000000299f0a0 60000000029a6a20 60000000029aa408
C Starting user session (con_hdl=0,svchp=60000000029aa338,srvhp=60000000029ac688,usrhp=60000000029a7238)
C *** ERROR => OCI-call 'OCISessionBegin' failed with rc=1017
[dboci.c      4532]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c    11044]
B ***LOG BY2=> sql error 1017   performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY2=> sql error 1017   performing CON [dblink#5 @ 431] [dblink 0431 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#5 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1435]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10377]
M
M Info for wp 10
M
M    stat = WP_RUN
M    waiting_for = NO_WAITING
M    reqtype = DP_RQ_BTCWP
M    act_reqtype = DP_RQ_BTCWP
M    rq_info = 8576
M    tid = -1
M    mode = 255
M    len = 24
M    rq_id = 1055
M    rq_source = FROM_WP_CA
M    last_tid = 10
M    last_mode = 0
M    semaphore = 0
M    act_cs_count = 0
M    csTrack = 0
M    csTrackRwExcl = 0
M    csTrackRwShrd = 0
M    mode_cleaned_counter = 0
M    control_flag = 0
M    int_checked_resource(RFC) = 0
M    ext_checked_resource(RFC) = 0
M    int_checked_resource(HTTP) = 0
M    ext_checked_resource(HTTP) = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M    req.vm = no VM
M    attachedVm = no VM
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   724]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 259]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc10 3549) [dpuxtool.c   259]
Do you have an idea how to get rid of this error? Did you experienced the same problem before? We will be thankful for any ideas.
Thank you all in advance.

Hi,
You did not mention abt the kerneleveland DB/SAP version details.
Chk the note 623242.
Regards.......

Uploading a file into DB error occured: ORA-01465: invalid hex number

While uploading a file into the DB, It is promting an error: "ORA-01465: invalid hex number"
how to convert a binary data to hex format in this case.

Hello again,
Ok, to upload into the database through APEX, using the file browser, you need to do the following:
1. Create the file browser item on your page.
2. Create a page process that is executed on the SUBMIT button.
The code should be something like this:
IF ( :P1_FILE_NAME is not null ) THEN
INSERT INTO oehr_file_subject(id,NAME, SUBJECT, BLOB_CONTENT, MIME_TYPE)
SELECT ID,:P1_FILE_NAME,:P1_SUBJECT,blob_content,mime_type
FROM APEX_APPLICATION_FILES
WHERE name = :P1_FILE_NAME;
DELETE from APEX_APPLICATION_FILES WHERE name = :P1_FILE_NAME;
END IF;{size:14}Files uploaded through the file browser are inserted into APEX_APPLICATION_FILES and need to be copied into your file.
Be sure to include a column in your table for the filename in {color:green}FILENAME.EXT{color} format so that the system will know how to handle the file when you try to download.
{size}
{size:14}
Don.
You can reward this reply by marking it as either Helpful or Correct :)
{size}

ORA-01722: invalid number when performing query

Hi,
I am running SQL Developer on a laptop (XP Pro) accessing Oracle Applications
Product Version     11.5.10.2
Platform     IBM SP AIX
OS Version     AIX
Database     9.2.0.7.0
Support ID     14460365
If I run the following query it works fine -
select
mtrh.request_number
,to_number(mtrh.request_number)
from
mtl_txn_request_headers mtrh
where
to_number(mtrh.request_number) = 135060
and mtrh.request_number = '135060' -- works with this line in!!!!
however if I comment out the last line I get
An error was encountered performing the requested operation :
ORA-01722: invalid number
The field request_number is defined as varchar2(30)
It seems that there is something strange about the way it handles to_number in where clauses.
Thanks
Mick Sulley

You have an invalid number in request_number. If you add "and mtrh.request_number = '135060' ", the result set will be reduced to only those rows which have 135060 in the column and the to_number() will work. WIthout that row, it does to_number(request_number) for all rows in order to identify the one you want. When it comes across a request_number column which contains an invalid number it reports an error.
<preach>
If request_number is a number then it should be stored in a number column. If it isn't, don't try an convert it to a number.
</preach>

ERROR: ORA-01017: invalid username/password; logon denied

Hi all
I need your kind help.
I have installed Oracle Audit Vault Server Release 10.2.3.2 in Linux system and collection agent in Windows system. Adding and starting DBAUD collector went fine however adding REDO collector return back errors when executing avorcldb add_collector command as follow
[oracle@avsrv ~]$
[oracle@avsrv ~]$ avorcldb add_collector -srcname orcl -agentname avagent01 -colltype REDO -av Lugaopc:1521:orcl
collector REDO_Collector for source orcl already exists
initializing REDO Collector
ERROR: could not get AV source user connection using jdbc:oracle:oci:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Lugaopc)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=orcl)))
ERROR: ORA-01017: invalid username/password; logon denied
[oracle@avsrv ~]$
Here is the contents of avorcldb.log file
09-09-13 16:58:44 [INFO ] Processing command add_collector
09-09-13 16:58:44 [INFO ] Processing arg -srcname = orcl
09-09-13 16:58:44 [INFO ] Processing arg -agentname = avagent01
09-09-13 16:58:44 [INFO ] Processing arg -colltype = REDO
09-09-13 16:58:44 [INFO ] Processing arg -av = Lugaopc:1521:orcl
09-09-13 16:58:44 [INFO ] Connect info : Lugaopc:1521:orcl
09-09-13 16:58:45 [INFO ] Got AV admin connection using jdbc:oracle:oci:@AVDB
09-09-13 16:58:45 [INFO ] Executing SQL as [ADM@AV] select s.host||':'||a1.num_value||':'||a2.char_value from avsys.av$attrvalue a1, avsys.av$attrvalue a2, avsys.av$source s, avsys.av$attrdef ad1, avsys.av$attrdef ad2 where source_name = :1 and a1.inst_id = s.source_id and a2.inst_id = s.source_id and a1.attr_id = ad1.attr_id and ad1.attr_name = 'PORT' and a2.attr_id = ad2.attr_id and ad2.attr_name = 'DB_SERVICE'
09-09-13 16:58:45 [INFO ] Using bind value orcl
09-09-13 16:58:45 [INFO ] Return value = Lugaopc:1521:orcl
09-09-13 16:58:45 [INFO ] Connect info : Lugaopc:1521:orcl
09-09-13 16:58:45 [INFO ] Executing SQL as [ADM@AV] select to_char(source_id) from avsys.av$source where source_name = :1
09-09-13 16:58:45 [INFO ] Using bind value orcl
09-09-13 16:58:45 [INFO ] Return value = 1
09-09-13 16:58:46 [INFO ] Got source user connection using jdbc:oracle:oci:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Lugaopc)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=orcl)))
09-09-13 16:58:46 [INFO ] Executing SQL as [ADM@AV] select decode(c.status, 1, 'active', 0, 'dropped', null) from avsys.av$collector c, avsys.av$source s where source_name = :1 and collector_name = :2 and c.source_id = s.source_id
09-09-13 16:58:46 [INFO ] Using bind value orcl
09-09-13 16:58:46 [INFO ] Using bind value REDO_Collector
09-09-13 16:58:46 [INFO ] Return value = active
09-09-13 16:58:46 [MESG ] collector REDO_Collector for source orcl already exists
09-09-13 16:58:46 [INFO ] Executing SQL as [ADM@AV] select decode(c.status, 1, 'active', 0, 'dropped', null) from avsys.av$collector c, avsys.av$source s where source_name = :1 and collector_name = :2 and c.source_id = s.source_id
09-09-13 16:58:46 [INFO ] Using bind value orcl
09-09-13 16:58:46 [INFO ] Using bind value REDO_Collector
09-09-13 16:58:46 [INFO ] Return value = active
09-09-13 16:58:46 [MESG ] initializing REDO Collector
09-09-13 16:58:46 [INFO ] Executing SQL as [ADM@AV] select username from avsys.av$source where source_name = :1
09-09-13 16:58:46 [INFO ] Using bind value orcl
09-09-13 16:58:46 [INFO ] Return value = AVSRCUSR1
09-09-13 16:58:46 [INFO ] Executing SQL as [ADM@AV] {? = call avsys.dbms_audit_vault.reset_source_user(?)}
09-09-13 16:58:46 [INFO ] Adding mask for user password
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] select table_name from user_tables where upper(table_name) = upper(:1)
09-09-13 16:58:46 [INFO ] Using bind value STREAMS_HEARTBEAT
09-09-13 16:58:46 [INFO ] Return value = STREAMS_HEARTBEAT
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] drop table streams_heartbeat
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] create table streams_heartbeat( src_dbname varchar2(4000), job_number number, heartbeat_time timestamp)
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] declare dbs_name varchar2(4000); begin select global_name into dbs_name from global_name; insert into streams_heartbeat values (dbs_name, 0, SYSTIMESTAMP); end;
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] create or replace procedure update_heartbeat IS begin update streams_heartbeat set heartbeat_time=(select systimestamp from dual); commit; end;
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] select table_name from user_tables where upper(table_name) = upper(:1)
09-09-13 16:58:46 [INFO ] Using bind value CAPTURE_RULES
09-09-13 16:58:46 [INFO ] Return value = CAPTURE_RULES
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] drop table capture_rules
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] create table capture_rules( rule_name varchar2(50), rule_scope varchar2(6), rule_type varchar2(3), obj_name   varchar2(100))
09-09-13 16:58:46 [INFO ] Executing SQL as [ADM@AV] select global_name from global_name
09-09-13 16:58:46 [INFO ] Return value = AVDB.AVSRV
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] select db_link from user_db_links where db_link = :1
09-09-13 16:58:46 [INFO ] Using bind value AVDB.AVSRV
09-09-13 16:58:46 [INFO ] Return value = AVDB.AVSRV
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] drop database link "AVDB.AVSRV"
09-09-13 16:58:46 [INFO ] Executing SQL as [USR@SRC] select version from v$instance
09-09-13 16:58:46 [INFO ] Return value = 11.2.0.1.0
09-09-13 16:58:46 [INFO ] Creating DB link using AVDB.AVSRV,AVSRCUSR1,{avsrcusr_pwd},Lugaopc,1521,orcl
09-09-13 16:58:46 [INFO ] Connecting as srcuser_ora01 to @(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Lugaopc)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=orcl)))
09-09-13 16:58:46 [INFO ] Output from SQLPlus
09-09-13 16:58:46 [INFO ]
09-09-13 16:58:46 [INFO ] Package created.
09-09-13 16:58:46 [INFO ]
09-09-13 16:58:46 [INFO ] No errors.
09-09-13 16:58:47 [INFO ]
09-09-13 16:58:47 [INFO ] Package body created.
09-09-13 16:58:47 [INFO ]
09-09-13 16:58:47 [INFO ] No errors.
09-09-13 16:58:47 [INFO ]
09-09-13 16:58:47 [INFO ] Package created.
09-09-13 16:58:47 [INFO ]
09-09-13 16:58:47 [INFO ] No errors.
09-09-13 16:58:47 [INFO ]
09-09-13 16:58:47 [INFO ] Package body created.
09-09-13 16:58:47 [INFO ]
09-09-13 16:58:47 [INFO ] No errors.
09-09-13 16:58:47 [INFO ] Executing SQL as [USR@SRC] select distinct name from user_errors where name = :1
09-09-13 16:58:47 [INFO ] Using bind value DBMS_SRC_STREAMS_COLLECTOR
09-09-13 16:58:47 [INFO ] Return value = null
09-09-13 16:58:47 [ERROR] could not get AV source user connection using jdbc:oracle:oci:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Lugaopc)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=orcl)))
09-09-13 16:58:47 [ERROR] ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
    at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:765)
    at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:414)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:546)
    at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:162)
    at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:53)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
    at java.sql.DriverManager.getConnection(DriverManager.java:525)
    at java.sql.DriverManager.getConnection(DriverManager.java:140)
    at oracle.av.avca.jdbc.JdbcConnection.<init>(JdbcConnection.java:87)
    at oracle.av.orcldb.DAO.initConnection(DAO.java:79)
    at oracle.av.orcldb.DAO.<init>(DAO.java:64)
    at oracle.av.orcldb.commands.AddCollector.setupCollector(AddCollector.java:746)
    at oracle.av.orcldb.commands.AddCollector.execute(AddCollector.java:230)
    at oracle.av.orcldb.Command.process(Command.java:89)
    at oracle.av.orcldb.Main.process(Main.java:118)
    at oracle.av.orcldb.Main.main(Main.java:132)
I have searched the forum to my level best without clear solution
Regards
Sadock

Hi gurus
I don't believe if this is missing solution from oracle community. I have decided to installed the collction agent and source database in linux system, so now both auditt vault server and collction agent are running in Linux system (but separately)
I am wondering, avorcldb add_collector -srcname ORCL -agentname avagent01 -colltype DBAUD and avorcldb add_collector -srcname ORCL -agentname avagent01 -colltype OSAUD -orclhome /u01/app/oracle/product/11.2.0/dbhome_1 are working fine and I am able to start these collectors
The avorcldb verify -src Lugaosrv:1521:ORCL.LUGAOSRV -colltype ALL command also return good results
[oracle@avsrv ~]$ avorcldb verify -src Lugaosrv:1521:ORCL.LUGAOSRV -colltype ALL
Enter Source user name: srcuser_ora01
Enter Source password:
source ORCL.LUGAOSRV verified for OS File Audit Collector collector
source ORCL.LUGAOSRV verified for Aud$/FGA_LOG$ Audit Collector collector
source ORCL.LUGAOSRV verified for REDO Log Audit Collector collector
[oracle@avsrv ~]$
The problem still I am facing is when attempting to add REDO collector. In fact the collector is added successful and i can see it even on EM console.
[oracle@avsrv ~]$ avorcldb add_collector -srcname ORCL -agentname avagent01 -colltype REDO -av Lugaosrv:1521:ORCL.LUGAOSRV
source ORCL verified for REDO Log Audit Collector collector
Adding collector...
Collector added successfully.
remember the following information for use in avctl
Collector name (collname): REDO_Collector
initializing REDO Collector
ERROR: could not get AV source user connection using jdbc:oracle:oci:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Lugaosrv)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ORCL.LUGAOSRV)))
ERROR: ORA-01017: invalid username/password; logon denied
[oracle@avsrv ~]$
Any help will be appreciated
Sadock

ORA-01017: invalid username/password; logon denied quality system refresh from production

Dear All;
I am in the post activities of SAP system refresh.
I restored the system using brtools successfully as you can see below:
then I went with the rest of the steps based on sap recomendations, and reached to SAP sql queries:
CREATE USER "OPS$<DOMAIN>\<SID>ADM" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;
CREATE USER "OPS$<DOMAIN>\SAPSERVICE<SID>" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;
GRANT CONNECT, RESOURCE, SAPDBA TO "OPS$<DOMAIN>\<SID>ADM";
GRANT CONNECT, RESOURCE, SAPDBA TO "OPS$<DOMAIN>\SAPSERVICE<SID>";
CREATE TABLE "OPS$<DOMAIN>\<SID>ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));
INSERT INTO "OPS$<DOMAIN>\<SID>ADM".SAPUSER VALUES ('SAPSR3', '<Password>');
CREATE SYNONYM "OPS$<DOMAIN>\SAPSERVICE<SID>".SAPUSER FOR "OPS$<DOMAIN>\<SID>ADM".SAPUSER;
CONNECT /
GRANT SELECT, UPDATE ON "OPS$<DOMAIN>\<SID>ADM".SAPUSER TO "OPS$<DOMAIN>\SAPSERVICE<SID>";
CONNECT /as sysdba
GRANT CONNECT, RESOURCE TO "OPS$<DOMAIN>\SAPSERVICE<SID>";
GRANT CONNECT, RESOURCE TO "OPS$<DOMAIN>\<SID>ADM";
I checked if all users are on opened state using select USERNAME,ACCOUNT_STATUS from dba_users;
The database is running file, and it is opened, but when I run R3trans -d it gives me RC 12 and i get this error:
*** ERROR => CONNECT failed with sql error '1017'
set_ocica() -> SQL error code 1017
-->oci_get_errmsg (con=0, rc=1017)
OCIErrorGet -> SQL error code: 1017
ORA-01017: invalid username/password; logon denied
DbSlConnect(con=0) -> orc=0, 99=DBSL_ERR_DB
***LOG BY2=>sql error 1017   performing CON
***LOG BY0=>ORA-01017: invalid username/password; logon denied
I used brconnect -u / -f chpass -o PSAPSR3 -p sap so i can reset the password, but still I am getting the same invalid username or password error.
I checked the listener status, and it is running.
Kindly let me know how I can fix my error
Best Regards
~Amal Aloun

Dear Gaurav;
I am running SAP Kernel 720 64bit unicode PL300
The content of my trans log file is the following:
4 ETW000 r3trans version 6.23 (release 720 - 15.05.12 - 20:12:03).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 05.08.2014 - 17:50:30
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [     dev trc,00000] Tue Aug 05 17:50:30 2014                                                 149 0.000149
4 ETW000 [     dev trc,00000] db_con_init called                                                        27 0.000176
4 ETW000 [     dev trc,00000] set_use_ext_con_info(): rsdb/ssfs_connect not set => ssfs not used        41 0.000217
4 ETW000 [     dev trc,00000] determine_block_commit: no con_hdl found as blocked for con_name = R/3
4 ETW000                                                                                                  28 0.000245
4 ETW000 [     dev trc,00000] create_con (con_name=R/3)                                                 14 0.000259
4 ETW000 [     dev trc,00000] Loading DB library 'dboraslib.dll' ...                                    44 0.000303
4 ETW000 [     dev trc,00000] DlLoadLib success: LoadLibrary("dboraslib.dll"), hdl 0, addr 000007FEF1650000
4 ETW000                                                                                                 947 0.001250
4 ETW000 [     dev trc,00000]      using "E:\usr\sap\TST\SYS\exe\uc\NTAMD64\dboraslib.dll"               18 0.001268
4 ETW000 [     dev trc,00000] Library 'dboraslib.dll' loaded                                            19 0.001287
4 ETW000 [     dev trc,00000] function DbSlExpFuns loaded from library dboraslib.dll                    23 0.001310
4 ETW000 [     dev trc,00000] Version of 'dboraslib.dll' is "720.00", patchlevel (0.215)               242 0.001552
4 ETW000 [     dev trc,00000] function dsql_db_init loaded from library dboraslib.dll                   26 0.001578
4 ETW000 [     dev trc,00000] function dbdd_exp_funs loaded from library dboraslib.dll                  34 0.001612
4 ETW000 [     dev trc,00000] New connection 0 created                                                 237 0.001849
4 ETW000 [     dev trc,00000] 0: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog =
4 ETW000                                                                                                  56 0.001905
4 ETW000 [     dev trc,00000] db_con_connect (con_name=R/3)                                             20 0.001925
4 ETW000 [     dev trc,00000] determine_block_commit: no con_hdl found as blocked for con_name = R/3
4 ETW000                                                                                                  25 0.001950
4 ETW000 [     dev trc,00000] find_con_by_name found the following connection:                          16 0.001966
4 ETW000 [     dev trc,00000] 0: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog =
4 ETW000                                                                                                  36 0.002002
4 ETW000 [     dev trc,00000] -->DbSlConnect(vers=-1, type=0, env='[default env]', userid='[default usr]')
4 ETW000                                                                                                  53 0.002055
4 ETW000 [     dev trc,00000] DIR_CLIENT_ORAHOME is not set as profile nor env. parameter.             574 0.002629
4 ETW000                        Assuming using instant client with unspecified location.
4 ETW000 [     dev trc,00000] Register application info.                                                97 0.002726
4 ETW000 [     dev trc,00000] Oracle client version: 10.2.0.4.0, (dbsl 720 220612, UNICODE[2])       10033 0.012759
4 ETW000 [     dev trc,00000] Detailed Oracle client (patch) info not available.                        30 0.012789
4 ETW000 [     dev trc,00000]    Default connection: tnsname ='TST'                                      73 0.012862
4 ETW000 [     dev trc,00000] -->oci_initialize(con=0, char='UTF16', nchar='AL16UTF16', nls=-1),uc_ln=2
4 ETW000                                                                                                  50 0.012912
4 ETW000 [     dev trc,00000] OCIEnvCreate(mode=16384=OCI_UTF16) returned 0 (for default NLS handle)
4 ETW000                                                                                                1828 0.014740
4 ETW000 [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrHp=027944B0)                 58 0.014798
4 ETW000 [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_ERROR, con=0, ErrBt=02796088)                 36 0.014834
4 ETW000 [     dev trc,00000] NLS env. settings: lang=41004D00450052004900430041004E00                 167 0.015001
4 ETW000 [     dev trc,00000]                     terr=41004D0045005200490043004100                      29 0.015030
4 ETW000 [     dev trc,00000]                     char=55005400460031003600                              22 0.015052
4 ETW000 [     dev trc,00000] Client NLS setting (by OCINlsGetInfo(con=0)): 'AMERICAN_AMERICA.UTF16'
4 ETW000                                                                                                  43 0.015095
4 ETW000 [     dev trc,00000] charset='UTF16', ncharset='AL16UTF16', UNI_ASC=FALSE                      19 0.015114
4 ETW000 [     dev trc,00000] Logon as OPS$-user to get SAPSR3's password                               28 0.015142
4 ETW000 [     dev trc,00000] Connecting as /@TST on connection 0 (nls 0) ... (dbsl 720 220612, UNICODE[2])
4 ETW000                                                                                                  61 0.015203
4 ETW000 [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_SVCCTX, con=0, svchp=02795F48)               370 0.015573
4 ETW000 [     dev trc,00000] Allocating server context handle                                          31 0.015604
4 ETW000 [     dev trc,00000] Attaching to database server TST (con=0, svchp=02795F48, srvhp=0279EFF8)
4 ETW000                                                                                                  74 0.015678
4 ETW000 [     dev trc,00000] Assigning server context 0279EFF8 to service context 02795F48          30008 0.045686
4 ETW000 [     dev trc,00000]     OCIHandleAlloc(OCI_HTYPE_SESSION, con=0, usrhp=027ABBE0)               86 0.045772
4 ETW000 [     dev trc,00000] Starting user session: OCISessionBegin(con=0, usr='/', svc=02795F48, srv=0279EFF8, usr=027ABBE0)
4 ETW000                                                                                                  40 0.045812
4 ETW000 [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with -1=OCI_ERROR               28164 0.073976
4 ETW000 [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:               95 0.074071
4 ETW000 [     dev trc,00000]     ORA-01017: invalid username/password; logon denied
4 ETW000                                                                                                  39 0.074110
4 ETW000 [    dbsloci.,00000] *** ERROR => CONNECT failed with sql error '1017'                         38 0.074148
4 ETW000 [     dev trc,00000]     set_ocica() -> SQL error code 1017                                     19 0.074167
4 ETW000 [     dev trc,00000] -->oci_get_errmsg (con=0, rc=1017)                                        20 0.074187
4 ETW000 [     dev trc,00000]     OCIErrorGet -> SQL error code: 1017                                    57 0.074244
4 ETW000 [     dev trc,00000]     ORA-01017: invalid username/password; logon denied
4 ETW000                                                                                                  39 0.074283
4 ETW000 [     dev trc,00000] Info: 99=DBSL_ERR_DB, oerr=1017, try to connect with default password.
4 ETW000                                                                                                  38 0.074321
4 ETW000 [     dev trc,00000] Connecting as SAPSR3/<pwd>@TST on connection 0 (nls 0) ... (dbsl 720 220612, UNICODE[2])
4 ETW000                                                                                                  30 0.074351
4 ETW000 [     dev trc,00000] Assigning username to user session: con=0, usrhp= 027ABBE0                23 0.074374
4 ETW000 [     dev trc,00000] Assigning password to user session: con=0, usrhp=027ABBE0                 36 0.074410
4 ETW000 [     dev trc,00000] Starting user session: OCISessionBegin(con=0, usr='SAPSR3', svc=02795F48, srv=0279EFF8, usr=027ABBE0)
4 ETW000                                                                                                 133 0.074543
4 ETW000 [     dev trc,00000] Tue Aug 05 17:50:40 2014                                             9992977 10.067520
4 ETW000 [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with -1=OCI_ERROR                  33 10.067553
4 ETW000 [     dev trc,00000]     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:               85 10.067638
4 ETW000 [     dev trc,00000]     ORA-01017: invalid username/password; logon denied
4 ETW000                                                                                                  37 10.067675
4 ETW000 [    dbsloci.,00000] *** ERROR => CONNECT failed with sql error '1017'                         29 10.067704
4 ETW000 [     dev trc,00000]     set_ocica() -> SQL error code 1017                                     19 10.067723
4 ETW000 [     dev trc,00000] -->oci_get_errmsg (con=0, rc=1017)                                        18 10.067741
4 ETW000 [     dev trc,00000]     OCIErrorGet -> SQL error code: 1017                                    55 10.067796
4 ETW000 [     dev trc,00000]     ORA-01017: invalid username/password; logon denied
4 ETW000                                                                                                  52 10.067848
4 ETW000 [     dev trc,00000]     DbSlConnect(con=0) -> orc=0, 99=DBSL_ERR_DB                            22 10.067870
4 ETW000 [    dblink ,00000] ***LOG BY2=>sql error 1017   performing CON                               58 10.067928
4 ETW000 [    dblink ,00000] ***LOG BY0=>ORA-01017: invalid username/password; logon denied            22 10.067950
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'TST'"
Best Regards
~Amal Aloun

ORA-28137: Invalid FGA audit Handler

Similar Messages

Maybe you are looking for