Skip to content

Siebel ERP Integration performance issue

Users are always complaint about siebel erp integration performance issue when they are doing push the approval data to erp r12. It will take approximately 2 to 4 minutes.

So I took the awr reports from both database  and crosschecked both with some interval, the siebel database performance is good but erp database saying there is integration related packages sql elasped time little bit more.

So i just went to siebel application and look the all components group log level ,How about ? Yes I found out there some of the components groups logging was enabled to 5, It should not be like always,  So I have decreased the default log level to 1 and clear that web service cache, and then I tried to push the transaction, it completed within 10 seconds.

And also i have disabled SOA auditing feature from ERP, Now data came within 4 seconds.

 

ORA-24247: network access denied by access control list (ACL)


SQL> begin
send_mail(‘test’,’azarmohds@gmail.com’);
end;
2 3 4
5 /
begin
*
ERROR at line 1:
ORA-24247: network access denied by access control list (ACL)
ORA-06512: at “SYS.UTL_TCP”, line 19
ORA-06512: at “SYS.UTL_TCP”, line 280
ORA-06512: at “SYS.UTL_SMTP”, line 163
ORA-06512: at “SYS.UTL_SMTP”, line 199
ORA-06512: at “SCOTT.SEND_MAIL”, line 8
ORA-06512: at line 2

This error message means that no access control list has been assigned to the host you (your application) are trying to access, or no required privileges have been granted to the user by adding user to the ACL.

Solution :

Step 1:  Conn as sysdba

BEGIN
DBMS_NETWORK_ACL_ADMIN.CREATE_ACL (
acl => ‘scottdev.xml’,
description => ‘Permissions to access ace-ins mail’,
principal => ‘SCOTT’,
is_grant => TRUE,
privilege => ‘connect’,
start_date => SYSTIMESTAMP,
end_date => NULL);
COMMIT;
END;
/

PL/SQL procedure successfully completed.

Step 2:

SQL> begin
2 DBMS_NETWORK_acl_ADMIN.ADD_PRIVILEGE(
3 acl => ‘scottdev.xml’,
4 principal => ‘SCOTT’,
5 is_grant => true,
6 privilege => ‘resolve’
7 );
8 COMMIT;
9 END;
10 /

PL/SQL procedure successfully completed.

Step 3:

SQL> BEGIN
DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL (
acl => ‘scottdev.xml’,
host => ‘*’);
COMMIT;
END;
/

 

step 4: Send mail as scott user

SQL> begin
send_mail(‘test’,’azarmohds@gmail.com’);
end; 2 3
4 /

PL/SQL procedure successfully completed.

failed to create user while installing oracle 12c in windows server 2012 R2

When  I am trying to install oracle 12c software in windows server 2012 r2, Its asking the windows user credentials. So I had given the windows new user “Test” and password like ” Test@123″ . Oracle installer accepted this password but windows not accepted this password because of password poilcy.

  • Atleast 8 characters inlcude letter, number, symbol
  • Also Don’t put your password letter as same like user name. It should not be identical.

Example :

User : Test

password : P@ssw0rd

Oracle 12c forms is released

Oracle 12c forms is released now. Please find the download link here

Issue When Trying To Generate The Custom WSDL ServiceGenerationError: Error In Service GenerationJ2T-120, ERROR: Illegal Option “-plsqlname=object

Please follow the note id

Issue When Trying To Generate The Custom WSDL ServiceGenerationError: Error In Service GenerationJ2T-120, ERROR: Illegal Option “-plsqlname=object (Doc ID 1619940.1)

Generate WSDL Command Errors With Inserted value too large for column (Doc ID 1913216.1)

Note : please check translator.jar file permission ,If It doesn’t have group permission , please

chmod g+w translator.jar

EBS 12.2.5 Release Update Pack Available

EBS 12.2.5 Release Update Pack Available (Patch 1967645

ref link EBS 12.2.5

Service Provider Access resulted in exception ‘oracle.apps.fnd.soa.util.SOAException: SystemError: Error while sending message to server. http://host.domain:8065/webservices/SOAProvider/EbizAuth?Generate= 3527

I have cloned our production environment (EBS version 12.1.3, DB 11.2.0.2) and then I have upgraded the database from 11.2.0.2 to 12.1.0.2.

and later We have requirement to enable integrate SOA gateway. So We were applied all the applicable patches at Production environment and enabled SOA also. So I thinking I have to enable asadmin and then I can able to generate wsdl through SOA. But When I tried , I am getting below error

“Service Provider Access resulted in exception ‘oracle.apps.fnd.soa.util.SOAException: SystemError: Error while sending message to server. http://xxxxxxx:8065/webservices/SOAProvider/EbizAuth?Generate=3527&soa_ticket=..’ when attempting to perform ‘GENERATE’. Please view Service Provider logs for more details”

and

http://xxxxxxxx:8065/webservices/SOAProvider/?testquery also return http 404 error.

Usually If we will get the above error If asadmin inactive or apps schema role are not defined for asadmin, So change the asadmin password and then we added the asadmin password in $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/config/system-jazn-data.xml and then restarted service, It will work.

But My case I did all the steps but Still I am getting error.

Solution :

When i upgraded the database 12c R2,  I was missed to add the below parameter in sqlnet.ora and sqlnet_ifile.ora file

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

After I have added the parameter in both files and restarted the application and database.

Its working fine

How to assign user management responsibility to user

  1. Log in as sysadmin
  2. Go to User management responsibility
  3. In users tab –> username –> Select your username
  4. Assign role –> Security Administrator
  5. Apply

ORA-16038 ORA-19809 ORA-00312

Database startup fails:

ORA-16038: log one sequence 3144 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312 online log 1 thread 1 <path to redo log file>

In the alert.log:
ORA-16014 signalled during: ALTER DATABASE open …
ORA-19815: WARNING: db_recovery_file_dest_size of xxx bytes is 100.00% used, and has 0 remaining bytes available.

solution :

support id : Flash Recovery Area Full – Database Fails to Open ORA-16038 (Doc ID 337258.1)

creating a pluggable database from an existing non-CDB Using the DBMS_PDB package

There are three ways of creating a pluggable database from an existing non-CDB:
• Using the DBMS_PDB package to generate metadata and then creating the pluggable database
with CREATE PLUGGABLE DATABASE SQL statement
• Data Pump (using the transportable tablespace feature)
• GoldenGate replication

Note :

When using the DBMS_PDB package to convert a non-CDB to a pluggable database, the non-CDB must be Oracle12c or higher.

Take care of your Non CDB and CDB chraceter set before pluggable database

In Oracle Database 12c, all pluggable databases (PDBs) in a container database (CDB) must have
* the same Database character set (NLS_CHARACTERSET) or the NLS_CHARACTERSET need to be a (Plug-in compatible) binary subset of the CDB NLS_CHARACTERSET
* the same National character set (NLS_NCHAR_CHARACTERSET)
  as the CDB’s root container
in order to be able to plug in.

If PDB NLS_CHARACTERSET is a (Plug-in compatible) binary subset of the CDB’s NLS_CHARACTERSET the NLS_CHARACTERSET of the PDB is automatically changed to the NLS_CHARACTERSET of the CDB at the first open.

 

more detail support id : 12c Multitenant Container Databases (CDB) and Pluggable Databases (PDB) Character set restrictions / ORA-65116/65119: incompatible database/national character set ( Character set mismatch: PDB character set CDB character set ) (Doc ID 1968706.1)

Step 1:  Non CDB in read only mode

SQL> select name from v$database;

NAME
———
ORA12C

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area 6710886400 bytes
Fixed Size 5298856 bytes
Variable Size 2835350872 bytes
Database Buffers 3858759680 bytes
Redo Buffers 11476992 bytes
Database mounted.
SQL> alter database open read only;

Database altered.

Step 2: run the DBMS_PDB package to create an XML file that describes the structure of the non-CDB database

SQL> BEGIN
DBMS_PDB.DESCRIBE(pdb_descr_file => ‘/u01/app/12c/ncdb.xml’);
END;
/ 2 3 4

PL/SQL procedure successfully completed.

Step 3: shutdown the non cdb database
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>

 

Step 4: connect to cdb container

SQL> show user con_id con_name
USER is “SYS”

CON_ID
——————————
1

CON_NAME
——————————
CDB$ROOT

Step 5: Now, you can optionally check to see if the non-CDB is compatible with the CDB in which it will be plugged.
When you run this code provide the directory and name of the XML file that was created previously

SQL> SET SERVEROUTPUT ON
DECLARE
hold_var boolean;
begin
hold_var := DBMS_PDB.CHECK_PLUG_COMPATIBILITY(pdb_descr_file=>’/u01/app/12c/ncdb.xml’);
if hold_var then
dbms_output.put_line(‘YES’);
else
dbms_output.put_line(‘NO’);
end if;
end;SQL> 2 3 4 5 6 7 8 9 10
11 /
YES

PL/SQL procedure successfully completed.

If there are no compatibility issues, a YES is displayed by the prior code; a NO is displayed if the pluggable database
is not compatible. You can query the contents of the PDB_PLUG_IN_VIOLATIONS view for details on why a pluggable
database is not compatible with a CDB.

Step 6: create pluggable database

SQL> CREATE PLUGGABLE DATABASE ora12c
USING ‘/u01/app/12c/ncdb.xml’
2 3 COPY
4 FILE_NAME_CONVERT = (‘/premia/app/12c/oracle/oradata/ora12c/’,
5 ‘/premia/app/12c/oracle/oradata/CDB/ora12c/’,’/premia/app/12c/oracle/product/dbhome_1/dbs/’,’/premia/app/12c/oracle/oradata/CDB/ora12c/’);

Pluggable database created.

Step 7:

SQL> select con_id, name from v$containers;

CON_ID NAME
———- ——————————
1 CDB$ROOT
2 PDB$SEED
3 HRPDB
4 ORA12C

Step 8:  Run the below script

SQL> alter session set container=ora12c;

Session altered.

SQL> show user con_id con_name user
USER is “SYS”

CON_ID
——————————
4

CON_NAME
——————————
ORA12C
USER is “SYS”

SQL> @/premia/app/12c/oracle/product/dbhome_1/rdbms/admin/noncdb_to_pdb.sql

Step 9:

SQL> select con_id,name,open_mode from v$containers;

CON_ID NAME OPEN_MODE
———- —————————— ———-
4 ORA12C MOUNTED

SQL> alter pluggable database ORA12C open;

Pluggable database altered.

Step 10:

SQL> conn test/test@ora12c
Connected.
SQL> select * from emp;

EMPNO
———-
1
2
3
4

4 rows selected.

 

Follow

Get every new post delivered to your Inbox.

Join 170 other followers