Quantcast
Channel: Doyensys Allappsdba Blog..
Viewing all 1640 articles
Browse latest View live

Get the Invalid objects details before and after apply the ad patches in oracle application

$
0
0
Get the Invalid objects details before and after apply the ad patches in oracle application.

In order to validate the invalid object list before and after the apply the patch, we can get know from the below logfile as follows,

Before apply the patch:

$APPL_TOP/admin/SID/log/50066_preenv.*

After apply the patch:

$APPL_TOP/admin/SID/log/50066_postenv.*

In the above logfile you came to know the invalid list changes for the patch

Error while running the pre-clone script on oracle application

$
0
0
When we run the pre-clone script we are getting the below error as follows,

$ perl adpreclone.pl dbTier

Perl lib version (v5.8.8) doesn't match executable version (v5.10.0) at <physical PATH>/perl_32/lib/5.8.8/IA64.ARCHREV_0-thread-multi/Config.pm line 46.
Compilation failed in require at <physical PATH>/db/tech_st/11.2.0/appsutil/clone/ouicli.pl line 35.
BEGIN failed--compilation aborted at <physical PATH>/db/tech_st/11.2.0/appsutil/clone/ouicli.pl line 35.


Cause:

The root cause has been identified with the template file 'adxdbctx.tmp' in Release 120.34.12010000.14 :

This template is used as part of the Contextfile generation, where it is pointing to Perl libraries in Release 5.8.3, which has been used for the Database in Release 10.2.x. With the Database Release 11.2.x the Perl Release referenced and used in the Environment to Release 5.10.

Part of the template file :
...
<PERL5LIB oa_var="s_perl5lib" osd="unix" default="%s_db_oh%%/%perl%/%lib%/%5.8.3:%s_db_oh%%/%perl%/%lib%/%site_perl%/%5.8.3:%s_db_oh%%/%appsutil%/%perl">%s_perl5lib%</PERL5LIB>
...

The PERL5LIB is pointing to Perl Release 5.8.3, which is producingthe failure.

This issue has been reported via unpublished Bug 10083614 - '12.2: CHANGE DEFAULT FOR VARIABLE S_PERL5LIB IN ADXDBCTX.TMP'. At this stage there is no Patch available.




Please use following workaround to get the failure fixed :

1. Make a backup copy of your existing Database Contextfile.

2. Modify the context file as shown.
BEFORE :

...
<PERL5LIB oa_var="s_perl5lib" osd="unix">/<complete path>/db/tech_st/11.2.0/perl/lib/5.8.3: \\
/<complete path>/db/tech_st/11.2.0/perl/lib/site_perl/5.8.3:/<complete path>/db/tech_st/11.2.0/appsutil/perl</PERL5LIB>
...

AFTER :

...
<PERL5LIB oa_var="s_perl5lib" osd="unix">/<complete path>/db/tech_st/11.2.0/perl/lib/5.10.0: \\
<complete path>/db/tech_st/11.2.0/perl/lib/site_perl/5.10.0:/<complete path>/db/tech_st/11.2.0/appsutil/perl</PERL5LIB>
...
3. Execute Autoconfig to get the modifications implemented.

4. Verify the Perl Release and the PER5LIB Environment Setting in your Enviornment :
4.1 perl -v
4.2 echo $PERL5LIB

The Perl release Information should be in synch with the Release used in the PERL5LIB Environment Setting.

ERROR WHILE IMPORTING THE SCHEMA

$
0
0
ERROR WHILE IMPORTING

ORA-31626: job does not exist
ORA-31637: cannot create job SYS_EXPORT_SCHEMA_01 for user SYS
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 600
ORA-39080: failed to create queues "KUPC$C_1_20100810134502" and "" for Data Pump job
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPC$QUE_INT", line 1606
ORA-24203: operation failed, queue table SYS.KUPC$DATAPUMP_QUETAB has errors

CAUSE:

Due to invalid object of sys

SQL> select object_name from all_objects where owner = 'SYS' AND status != 'VALID' order by 1;

OBJECT_NAME
------------------------------
AQ$KUPC$DATAPUMP_QUETAB
AQ$_KUPC$DATAPUMP_QUETAB_E
AQ$_KUPC$DATAPUMP_QUETAB_F
AQ$_KUPC$DATAPUMP_QUETAB_V
KUPC$DATAPUMP_QUETAB
SYSNTK+Hp6PazTJaPOReVq6YXqQ==
SYSNTsDyaSCdvTmySdAs5Ztvhbw==
SYSNTWBJ9iDeeSuyp/p6B7f1iEg==

8 rows selected.

SOLUTION:

Recreate queue tables,that were invalid

SQL> exec dbms_aqadm.drop_queue_table(queue_table =>'SYS.KUPC$DATAPUMP_QUETAB', force=> TRUE);

PL/SQL procedure successfully completed.




SQL> BEGIN
  2  dbms_aqadm.create_queue_table(queue_table =>                                               'SYS.KUPC$DATAPUMP_QUETAB',
  3    multiple_consumers => TRUE,
  4    queue_payload_type =>'SYS.KUPC$_MESSAGE',
  5    comment => 'DataPump Queue Table',
  6    compatible=>'10.1.0');
  7  EXCEPTION
  8    WHEN OTHERS THEN
  9      IF SQLCODE = -24001 THEN NULL;
 10      ELSE RAISE;
 11      END IF;
 12  END;
 13  /

PL/SQL procedure successfully completed.

Let's check invalids again:

SQL> select object_name from all_objects where owner = 'SYS' AND status != 'VALID' order by 1;

no rows selected


REP-58100: An error occurred starting the internal Web server at port $$Self.OHSPort$$. Error: java.lang.NumberFormatException:For input string: "$$Self.OHSPort We faced this error when we run the report in weblayout.

$
0
0
ERROR:
----------
REP-58100: An error occurred starting the internal Web server at port $$Self.OHSPort$$.
Error: java.lang.NumberFormatException:For input string: "$$Self.OHSPort
We faced this error when we run the report in weblayout.

Cause:
This is a plugin parameter whic should be added in rwbuilder.conf file after report builder is installed.

Solution :

1) Go the the below location  u01/app/oracle/config/domain/frsdomain/config/fmwconfig/components/ReportsToolsComponent/report_server1

2) Vi rwbuilder.conf

3) Add the below parameter :

<webLayout port="9002" docroot="/u01/app/oracle/config/domain/frsdomain/servers/WLS_REPORTS/tmp/_WL_user/reports_12.2.1/5ah7s6/war"/>

4) Link for fixing the above problem.
https://docs.oracle.com/middleware/1221/formsandreports/install-fnr/install.htm#CIHGBBEH


FRM:18124 failed to start one button run HTTP server to run form on web

$
0
0
FRM:18124 failed to start one button run HTTP server to run form on web

Cause:
In the runtime preferences the default URL will be invalid. We have to enter the proper path of browser.

Solution:
Open form builder
[oracle@forms bin]$ frmbld

Go to Edit --> Preferences --> Runtime

The Application Server URL will be in default. We have to provide the path of browser installed.

The below provided paths can be given in the Application Server URL :

1) /usr/lib/firefox-3.6.9
2) http://forms.doyensys.com:9001/forms/frmservlet



REP-51019 system user authentication is missing in oracle reports 12c

$
0
0
REP-51019 system user authentication is missing

1)  In  rwservlet.properties confirm SSO is already disabled:
<singlesignon>no</singlesignon>


2) Disable JAZN security.  In rwserver.conf that belongs to the reports server you will use (in-process, standalone or both) change the following entry:
...
<security class="oracle.reports.server.RWJAZNSecurity" id="rwJaznSec"/>
...
<job jobType="report" engineId="rwEng" securityId="rwJaznSec"/>
...

Add "!--" at the beginning and "--" at the end, in order oracle.reports.server.RWJAZNSecurity is commented:

<!--security class="oracle.reports.server.RWJAZNSecurity" id="rwJaznSec"/-->

and delete securityId="rwJaznSec" in jobType="report":

<job jobType="report" engineId="rwEng"/>

Old Value:

<job jobType="report" engineId="rwEng" securityId="rwJaznSec"/>

New Value:

<job jobType="report" engineId="rwEng"/>

3) Restart the reports server to apply the changes.

 If it was the in-process reports server, or you applied changes in rwservlet.properties, you need to restart WLS_REPORTS.


LOAD JAVA FILES TO THE DB USER

$
0
0
[oracle@localhost jlib]$ loadjava -user HR mail.jar

Password:
********                                                                                                                                                              
[oracle@localhost jlib]$ !sq
sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Thu Apr 28 14:35:20 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options



SQL>  begin dbms_java.grant_permission( 'HR', 'SYS:java.net.SocketPermission','localhost:PORT','connect,resolve');end;
  2  /

PL/SQL procedure successfully completed.

SQL> BEGIN dbms_java.grant_permission( 'HR','SYS:java.net.SocketPermission', 'zpop.hybridzimbra.com', 'resolve' );end;
  2  /

PL/SQL procedure successfully completed.


ORA-27492: unable to run job “APEX_040200.ORACLE_APEX_MAIL_QUEUE”: scheduler unavailable

$
0
0
ISSUE:
----------------
ORA-27492: unable to run job “APEX_040200.ORACLE_APEX_MAIL_QUEUE”: scheduler unavailable


SOLUTIONS:
------------------------

Alter system set job_queue_processes=1000;

Report Builder is not working

$
0
0
Error in Report Builder :

While running the rwbuilder.sh it has thrown error.


Cause:
The domain home was not set properly in the rwbuilder.sh


Solution:

To run the report builder we changed the DOMAIN_HOME in the rwbuilder.sh

Vi rwbuilder.sh
Change the DOMAIN_HOME=$$domain_home$$
To 
DOMAIN_HOME=/u01/app/oracle/config/domain/frsdomain


11gR2 RAC ASM using RMAN Multiplexing the control file

$
0
0

STEP 1. Check the current control file status 

SQL> select name from v$controlfile;
NAME
——————————————————————————–

+DATA/orcl/controlfile/current.263.800282297

STEP 2. Change the  control_files parameter by adding the new disk group

Alter system set control_files='+DATA/orcl/controlfile/current.263.800282297','+FRA' scope=spfile;

STEP 3. Shutdown the RAC database and start the database in nomount mode

srvctl stop database -d orcl

srvctl start database -d orcl -o nomount


STEP 4. After bounce and check the database and see if new diskgroup has been added to the control_files parameter

 SQL> show parameter control_files
NAME                                     TYPE                         VALUE
 ———————————— ———– ——————————————————————————-

 control_files                      string                      +DATA/orcl/controlfile/current.263.800282297, +FRA

STEP 5. Connect to RMAN and use restore command to create a copy of the control file

oracle@node1]$ rman target /
Recovery Manager: Release 11.2.0.3.0 – Production on Wed MAY 28 04:50:08 2016
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: orcl (not mounted)
RMAN> restore controlfile from '+DATA/orcl/controlfile/current.263.800282297';
Starting restore at 28-MAY-16
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=377 instance=orcl1 device type=DISK
channel ORA_DISK_1: copied control file copy
output file name=+DATA/orcl/controlfile/current.263.800282297
output file name=+OCR_VOTE/orcl/controlfile/current.256.800513469

Finished restore at 28-MAY-16

Step:8 Check the controlfile name in ASM diskgroup "FRA"

As you can see above new control file

+FRA/orcl/controlfile/current.256.800513469 has been generated.

STEP 9.modify the control_files parameter using alter system command


 SQL> alter system set control_files='+DATA/orcl/controlfile/current.263.800282297', '+FRA/orcl/controlfile/current.256.800513469' scope=spfile;

STEP 10. Shutdown the database and start up normal.

[gridora@node1$ srvctl stop database -d orcl
[gridora@node1$ srvctl start database -d orcl

SQL> show parameter control_files;
NAME                 TYPE        VALUE
 ———————————— ——————————– —————————————————————–————
 control_files     string    +DATA/orcl/controlfile/current.263.800282297, +FRA/orcl/controlfile/current.256.800513469


SQL> select name from v$controlfile;
NAME
 ————————————————————————————————
 +DATA/orcl/controlfile/current.263.800282297
 +FRA/orcl/controlfile/current.256.800513469



Top 10 - Biggest Tables and Indexes

$
0
0
set lines 170
set pages 20
col owner      format a20
col object     format a30
col type       format a6
col tablespace format a20
col size_in_gb format 999,999.9
select * 
  from (select owner           owner,
               segment_name    object,
               segment_type    type,
               tablespace_name tablespace,
               round(bytes/1024/1024/1024,1) size_in_gb
          from dba_segments 
         where owner not in ('SYS','SYSTEM')
         order by bytes desc
       ) 
 where rownum < 11
 order by size_in_gb desc;

IDENTIFYING CORRUPTION SEGMENTS

$
0
0
set linesize 140
col owner format a10
col segment_type format a10
col segment_name format a30
col partition_name format a15
col file# format 999
SELECT e.owner, e.segment_type, e.segment_name, e.partition_name, c.file#
       , greatest(e.block_id, c.block#) corr_start_block#
       , least(e.block_id+e.blocks-1, c.block#+c.blocks-1) corr_end_block#
       , least(e.block_id+e.blocks-1, c.block#+c.blocks-1) 
         - greatest(e.block_id, c.block#) + 1 blocks_corrupted
       , null description
    FROM dba_extents e, v$database_block_corruption c
   WHERE e.file_id = c.file#
     AND e.block_id <= c.block# + c.blocks - 1
     AND e.block_id + e.blocks - 1 >= c.block#
  UNION
  SELECT s.owner, s.segment_type, s.segment_name, s.partition_name, c.file#
       , header_block corr_start_block#
       , header_block corr_end_block#
       , 1 blocks_corrupted
       , 'Segment Header' description
    FROM dba_segments s, v$database_block_corruption c
   WHERE s.header_file = c.file#
     AND s.header_block between c.block# and c.block# + c.blocks - 1
  UNION
  SELECT null owner, null segment_type, null segment_name, null partition_name, c.file#
       , greatest(f.block_id, c.block#) corr_start_block#
       , least(f.block_id+f.blocks-1, c.block#+c.blocks-1) corr_end_block#
       , least(f.block_id+f.blocks-1, c.block#+c.blocks-1) 
         - greatest(f.block_id, c.block#) + 1 blocks_corrupted
       , 'Free Block' description
    FROM dba_free_space f, v$database_block_corruption c
   WHERE f.file_id = c.file#
     AND f.block_id <= c.block# + c.blocks - 1
     AND f.block_id + f.blocks - 1 >= c.block#
  order by file#, corr_start_block#
/

Error while running the autoconfig on the apps Node

$
0
0
Error:


Autoconfig could not process the following files:
    Directory: /u01/app/oracle/inst/apps/SVRPRD_svrprdebsal1/ora/10.1.3/Apache/Apache/bin
      .apachectl              BINCPY
      .apachectl              BINCPY

AutoConfig is exiting with status 2

Solution :

The workaround for this is simply to change the permissions on .apachectl, run AutoConfig, and then put them back:

1. As applmgr, stop the web tier services (adopmnctl.sh stop).

2. Switch to the root user (su root)

3. Run the following commands (assumes applmgr environment and that "applmgr" is your actual applmgr user name):
    a.  ls -l $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl
    b.  chown applmgr $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl
    c.  chmod 0700 $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl
    d.  ls -l $ORA_CONFIG_HOME/10.1.3/Apache/Apache/bin/.apachectl

4. Switch back to the applmgr user (exit)

5. Run AutoConfig 

6. Reverse step 3 so that the result looks like step 3a:
    a. su root
    b. chown root .apachectl
    c. chmod 6750 .apachectl 
    d. exit

How to change passwords to include special characters using FNDCPASS

$
0
0
Note that the term 'Special Characters' is used in this article to refer to those characters who are shown in the table below.

Use of the FNDCPASS utility to change the passwords of database users such as APPS , APPLSYS, GL etc to include special characters is NOT supported .
If an attempt is made to use FNDCPASS to include a special character in the password for a database user one of the following errors will typically be encountered . 

1. Cause: changepassword failed due to ORA-01403: no data found.

2. syntax error: unexpected end of file

3. syntax error near unexpected token `newline'

4. APP-FND-02704: Unable to alter user APPS to change password.

5. APP-FND-01564: ORACLE error 1017 in AFPCOA

6. FNDCPASS was not able to decrypt password for user 'APPS' during applsys password change.

7. Passwords must be at least 5 characters long. ( This error can be encountered even when password is > 5 characters long) 

Which error is encountered depends on the factors such as which database user is having their password changed , which special character is being used and the position where the special character appears in the password ( eg first character of password or second character etc) 

It is possible to use FNDCPASS to change the password of an EBS user such as SYSADMIN and include one or more special characters of those listed below although there are some provisos for some characters which are described in table below. In certain cases it may be necessary to include the new password in quotation marks 

Example 1
=========

FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN !welcome1

In this example the password of EBS user SYSADMIN is changed to !welcome1 and no quotation marks are required . 

Example 2
=========

FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN $welcome1

This attempt to change the password will FAIL and the log file created will contain an error message.

Example 3
=========
FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN '$welcome1'

By modifying Example 2 by adding quotation marks this example will work and the password will be changed to $welcome1 .




adapcctl.sh: exiting with status 204 in oracle apps

$
0
0
Error:

You are running adapcctl.sh version 120.7.12010000.2

Starting OPMN managed Oracle HTTP Server (OHS) instance ...

adapcctl.sh: exiting with status 204

Cause:

.apachectl has permission denied to run the apache services.

Solution:


Go to $INST_TOP/ora/10.1.3/Apache/Apache/bin (As root user).

Change the owner and assign the permission


chown root .apachectl

chmod 6750 .apachectl






Article 6

$
0
0
                                 

                                       Query to find all responsibilities of a user in oracle apps





SELECT fu.user_name                "User Name",
       frt.responsibility_name     "Responsibility Name",
       furg.start_date             "Start Date",
       furg.end_date               "End Date",    
       fr.responsibility_key       "Responsibility Key",
       fa.application_short_name   "Application Short Name"
  FROM fnd_user_resp_groups_direct        furg,
       applsys.fnd_user                   fu,
       applsys.fnd_responsibility_tl      frt,
       applsys.fnd_responsibility         fr,
       applsys.fnd_application_tl         fat,
       applsys.fnd_application            fa
 WHERE furg.user_id             =  fu.user_id
   AND furg.responsibility_id   =  frt.responsibility_id
   AND fr.responsibility_id     =  frt.responsibility_id
   AND fa.application_id        =  fat.application_id
   AND fr.application_id        =  fat.application_id
   AND frt.language             =  USERENV('LANG')
   AND UPPER(fu.user_name)      =  UPPER('&USERNAME')  -- <change it>
   -- AND (furg.end_date IS NULL OR furg.end_date >= TRUNC(SYSDATE))
 ORDER BY frt.responsibility_name;



Article 5

$
0
0

Steps to configure a BATCHSQL mode in Oracle GoldenGate 


How to do it...

The BATCHSQL mode can be configured by adding the following parameters in the replicat
configuration file:


       REPLICAT RGGTEST1
       USERID GGATE_ADMIN@TGORTEST, PASSWORD GGATE_ADMIN
       DISCARDFILE /u01/app/ggate/dirrpt/RGGTEST1.dsc,append,MEGABYTES 500
       ASSUMETARGETDEFS
       MAP SCOTT.*, TARGET SCOTT.*;
       BATCHSQL BATCHPERQUEUE 100, OPSPERBATCH 200

Article 4

$
0
0
Performing a healthcheck of a live GoldenGate configuration



How to do it...

The state of a GoldenGate replication can be checked by performing the following steps on
both source and target systems:

1. Check the GoldenGate event logger file ggserr.log for any error or warning
messages. You can find these messages using the egrep command as shown
in the following code:

     cd /u01/app/ggate
     egrep –i 'WARNING|ERROR' ggserr.log | more

2. Using the GoldenGate command line interface, check the status of the processes
as follows:

     GGSCI (prim1-ol6-112.localdomain) 1> status *
     EXTRACT EGGTEST1: RUNNING
     EXTRACT PGGTEST1: ABENDED

The status of all processes should be RUNNING.

3. If the status of any of the processes is not RUNNING, check the Process Report
files under $GG_HOME/dirrpt/. For example, for the PGGTEST1 process that has
an ABENDED status you should look for the error in the /u01/app/ggate/dirrpt/
PGGTEST1.rpt report file.

4. If the process is abended due to any data issue, you will see an ORA-error in
the Process Report file. GoldenGate writes failed record information to the
discard file.

5. If all the processes are running, check the lag between the systems as shown in the
following code:

     GGSCI (prim1-ol6-112.localdomain) 1> lag *
     Sending GETLAG request to EXTRACT EGGTEST1 ...
     Last record lag: 5 seconds.
     At EOF, no more records to process.
     Sending GETLAG request to EXTRACT PGGTEST1 ...
     Last record lag: 6 seconds.
     At EOF, no more records to process.

6. Sometimes there can be an issue with the underlying database due to which the
GoldenGate processes can abend. The state of the database can be checked from
the database alert log.

Article 3

Article 2

Viewing all 1640 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>