Monday, 19 September 2016

ORA-04031

ORA-04031: unable to allocate 4064 bytes of shared memory ("shared pool","select increment$,minvalue,m...","sga heap(3,0)","kglsim heap")

Solution:-

# ps -ef|grep oracle


find the smon and kill the pid for it.

# Kill -9 

SQL> startup mount
ORACLE instance started.
Total System Global Area 4831838208 bytes Fixed Size 2027320 bytes Variable Size 4764729544 bytes Database Buffers 50331648 bytes Redo Buffers 14749696 bytes Database mounted. SQL>

SQL> alter system set shared_pool_size=100M scope=spfile;

System altered.

SQL> shutdown immediate

ORA-01109: database not open
Database dismounted. ORACLE instance shut down.

SQL> startup

ORACLE instance started.
Total System Global Area 4831838208 bytes Fixed Size 2027320 bytes Variable Size 4764729544 bytes Database Buffers 50331648 bytes Redo Buffers 14749696 bytes Database mounted. Database opened.

SQL> create pfile from spfile;

File created.

OR

Oracle 11G

For implementation in Oracle 11g startup database in mount mode:

$ export ORACLE_SID=[instance]
$ sqlplus sys as sysdba

SQL> startup mount
ORACLE instance started.
Total System Global Area 1000189952 bytes
Fixed Size                  1337492 bytes
Variable Size             708839276 bytes
Database Buffers          285212672 bytes
Redo Buffers                4800512 bytes
Database mounted.

SQL> alter system set memory_max_target=2000m scope=spfile;
System altered.

SQL> alter database open;
ORACLE instance started.
Total System Global Area 1000189952 bytes
Fixed Size                  1337492 bytes
Variable Size             708839276 bytes
Database Buffers          285212672 bytes
Redo Buffers                4800512 bytes
Database mounted.
Database opened. 

SQL> alter system set memory_target=1600m;
System altered.

Oracle 10G

 For implementation in Oracle 10g startup database in mount mode:

$ export ORACLE_SID=[instance]

$ sqlplus sys as sysdba

SQL> startup mount
ORACLE instance started.
Total System Global Area 1000189952 bytes
Fixed Size                  1337492 bytes
Variable Size             708839276 bytes
Database Buffers          285212672 bytes
Redo Buffers                4800512 bytes
Database mounted.

SQL> alter system set sga_max_size=2000M scope=spfile;
System altered.

SQL> alter database open;
ORACLE instance started.
Total System Global Area 1000189952 bytes
Fixed Size                  1337492 bytes
Variable Size             708839276 bytes
Database Buffers          285212672 bytes
Redo Buffers                4800512 bytes
Database mounted.
Database opened. 

SQL> alter system set sga_target=1600m scope=spfile;;

System altered.

Issue resolved.

Thursday, 15 September 2016

The referenced database doesn't contain a valid management Repository.


OMS 13c agent installation failed with "The referenced database doesn't contain a valid management Repository."

Cause :-

Generally this error comes when the database we are using as OMS database was already used as a database for OMS installation before or A failed OMS installation already happened using this database.


Error:-
The referenced database doesn't contain a valid management Repository.



Solution :-

we have to properly clean the database before using it again as a OMS database :-

Below steps I did to clean my database :-

1. Drop sysman related schemas.

[ACSDB@acs-oem13c ~]$ . .bash_profile
[ACSDB@acs-oem13c ~]$ sqlplus / as sysdba

SQL> DROP USER SYSMAN CASCADE;

User dropped.
SQL> DROP USER SYSMAN_OPSS CASCADE;

User dropped.

SQL> DROP USER SYSMAN_MDS CASCADE;

User dropped.

SQL> DROP USER SYSMAN_STB CASCADE;

User dropped.

SQL> DROP USER SYSMAN_BIPLATFORM CASCADE;

User dropped.


SQL> DROP USER SYSMAN_RO CASCADE;

User dropped.

2. Remove Synonyms related to sysman accounts :-

DECLARE
  CURSOR l_syn_csr IS
    SELECT 'DROP ' ||
      CASE owner
        WHEN 'PUBLIC'
          THEN 'PUBLIC SYNONYM '
        ELSE 'SYNONYM ' || owner || '.'
      END ||
      synonym_name AS cmd
    FROM
      dba_synonyms
    WHERE
      table_owner IN (
        'SYSMAN',
        'SYSMAN_MDS',
        'MGMT_VIEW',
        'SYSMAN_BIP',
        'SYSMAN_APM',
        'BIP',
        'SYSMAN_OPSS',
        'SYSMAN_RO'
      );
BEGIN
  FOR l_syn_rec IN l_syn_csr LOOP
    BEGIN
      EXECUTE IMMEDIATE l_syn_rec.cmd;
    EXCEPTION
      WHEN OTHERS THEN
        dbms_output.put_line( '===> ' || l_syn_rec.cmd );
        dbms_output.put_line( sqlerrm );
    END;
  END LOOP;
END;
/


PL/SQL procedure successfully completed.


3. Removing remaining Objects and tablespaces :-


SQL> DROP USER mgmt_view CASCADE;

User dropped.

SQL> DROP TABLESPACE mgmt_ecm_depot_ts INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS;

Tablespace dropped.

SQL> DROP TABLESPACE mgmt_tablespace   INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS;

Tablespace dropped.

SQL> DROP TABLESPACE mgmt_ad4j_ts      INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS;

Tablespace dropped.



4.  As proper database cleaning using RepManager dropall didn't happen, so we have to clean up the registry details :-

DELETE
  FROM
    schema_version_registry
  WHERE
    (comp_name,owner) IN (
      ('Authorization Policy Manager','SYSMAN_APM'),
      ('Metadata Services','SYSMAN_MDS'),
      ('Oracle Platform Security Services','SYSMAN_OPSS')
    );

2 rows deleted.
SQL> commit;

Commit complete.

SQL> ALTER SYSTEM SET optimizer_dynamic_sampling = 0 SCOPE=both;

System altered.










Wednesday, 14 September 2016

How To Resize the Online Redo Logfiles

1. First see the size of the current logs:

> sqlplus /nolog
SQL> connect / as sysdba

SQL> select group#, bytes, status from v$log;
GROUP# BYTES STATUS
———- ———- —————-
1 1048576 INACTIVE
2 1048576 CURRENT
3 1048576 INACTIVE

Logs are 1MB from above, let’s size them to 10MB.

2. Retrieve all the log member names for the groups:

SQL> select group#, member from v$logfile;

GROUP# MEMBER
————— —————————————-
1 /usr/oracle/dbs/log1PROD.dbf
2 /usr/oracle/dbs/log2PROD.dbf
3 /usr/oracle/dbs/log3PROD.dbf

3. Let’s create 3 new log groups and name them groups 4, 5, and 6, each 10MB in size:

SQL> alter database add logfile group 4  '/usr/oracle/dbs/log4PROD.dbf' size 10M;
  SQL> alter database add logfile group 5  '/usr/oracle/dbs/log5PROD.dbf' size 10M;
   SQL> alter database add logfile group 6  '/usr/oracle/dbs/log6PROD.dbf' size 10M;
4. Now run a query to view the v$log status:

 SQL> select group#, status from v$log;
GROUP# STATUS
--------- ----------------
1 INACTIVE
2 CURRENT

3 INACTIVE

4 UNUSED

5 UNUSED

6 UNUSED

From the above we can see log group 2 is current, and this is one of the
smaller groups we must drop. Therefore let’s switch out of this group into
one of the newly created log groups.

5. Switch until we are into log group 4, so we can drop log groups 1, 2, and 3:

SQL> alter system switch logfile;
** repeat as necessary until group 4 is CURRENT **

6. Run the query again to verify the current log group is group 4:

SQL> select group#, status from v$log;

GROUP# STATUS
——— —————-
1 INACTIVE
2 INACTIVE
3 INACTIVE
4 CURRENT
5 UNUSED
6 UNUSED

Note: redo log Group 1 or 2 or 3 can be active after “alter system switch log file”
which means could not be dropped, in this case,
you need to do “alter system checkpoint” to make redo log groups 1,2 and 3 inactive.

7. Now drop redo log groups 1, 2, and 3:

SQL> alter database drop logfile group 1;
SQL> alter database drop logfile group 2;
SQL> alter database drop logfile group 3;

Verify the groups were dropped, and the new groups’ sizes are correct.

SVRMGR> select group#, bytes, status from v$log;

GROUP# BYTES STATUS
——— ——— —————-
4 10485760 CURRENT
5 10485760 UNUSED
6 10485760 UNUSED

8. At this point, you consider taking a backup of the database.

9. You can now go out to the operating system and delete the files associated
with redo log groups 1, 2, and 3 in step 2 above as they are no longer
needed:

% rm /usr/oracle/dbs/log1PROD.dbf
% rm /usr/oracle/dbs/log2PROD.dbf
% rm /usr/oracle/dbs/log3PROD.dbf

How to resize redo logfile group in Oracle RAC.

1. First see the size of the current logs:

SQL> select group#, bytes, status from v$log;

GROUP# BYTES STATUS
———- ———- —————-
21 1073741824 INACTIVE
22 1073741824 CURRENT
23 1073741824 INACTIVE
24 1073741824 INACTIVE
25 1073741824 INACTIVE
26 1073741824 INACTIVE
27 1073741824 INACTIVE
28 1073741824 ACTIVE
29 1073741824 CURRENT
30 1073741824 INACTIVE
31 1073741824 INACTIVE
32 1073741824 INACTIVE

12 rows selected.

Logs are 1GB from above, let’s size them to 500MB.

2. Retrieve all the log member names for the groups:

SQL> select group#, member from v$logfile;

GROUP#
———-
MEMBER
——————————————————————————–
31
+DATA/prod/onlinelog/group_31.391.787059447

32
+DATA/prod/onlinelog/group_32.390.787059453

21
+DATA/prod/onlinelog/group_21.258.787054781

22
+DATA/prod/onlinelog/group_22.256.787054787

23
+DATA/prod/onlinelog/group_23.274.787054793

24
+DATA/prod/onlinelog/group_24.273.787054799

25
+DATA/prod/onlinelog/group_25.271.787054805

26
+DATA/prod/onlinelog/group_26.394.787054839

27
+DATA/prod/onlinelog/group_27.395.787054845

28
+DATA/prod/onlinelog/group_28.396.787054851

29
+DATA/prod/onlinelog/group_29.397.787054855

30
+DATA/prod/onlinelog/group_30.398.787054861
12 rows selected.
3- Let’s create 3 new log groups per instance and name them groups 40,41,42 and 50,51 and 52 and each 500MB in size:

SQL> ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 40 '+DATA' SIZE 500m;
Database altered.

SQL> ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 41 '+DATA' SIZE 500m;
Database altered.

SQL> ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 42 '+DATA' SIZE 500m;
Database altered.

SQL> ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 50 '+DATA' SIZE 500m;
Database altered.

SQL> ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 51 '+DATA' SIZE 500m;
Database altered.

SQL> ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 52 '+DATA' SIZE 500m;
Database altered.

4. Now run a query to view the v$log status:

SQL> select group#, bytes, status from v$log;
GROUP# BYTES STATUS
---------- ---------- ----------------
 21 1073741824 INACTIVE
 22 1073741824 CURRENT
 23 1073741824 INACTIVE
 24 1073741824 INACTIVE
 25 1073741824 INACTIVE
 26 1073741824 INACTIVE
 27 1073741824 INACTIVE
 28 1073741824 ACTIVE
 29 1073741824 CURRENT
 30 1073741824 INACTIVE
 31 1073741824 INACTIVE
 32 1073741824 INACTIVE
 40 524288000 UNUSED
 41 524288000 UNUSED
 42 524288000 UNUSED
 50 524288000 UNUSED
 51 524288000 UNUSED
 52 524288000 UNUSED
18 rows selected.

5. Now drop Unactive redo log group


SQL> alter database drop logfile group 21;
Database altered.

SQL> alter database drop logfile group 23;
Database altered.

SQL> alter database drop logfile group 24;
Database altered.

SQL> alter database drop logfile group 25;
Database altered.

SQL> alter database drop logfile group 26;
Database altered.

SQL> alter database drop logfile group 27;
Database altered.

SQL> alter database drop logfile group 30;
Database altered.

SQL> alter database drop logfile group 31;
Database altered.

SQL> alter database drop logfile group 32;
Database altered.


SQL> select group#, bytes, status from v$log;

GROUP# BYTES STATUS
———- ———- —————-
22 1073741824 CURRENT
28 1073741824 ACTIVE
29 1073741824 CURRENT
40 524288000 UNUSED
41 524288000 UNUSED
42 524288000 UNUSED
50 524288000 UNUSED
51 524288000 UNUSED
52 524288000 UNUSED

9 rows selected.

Thursday, 8 September 2016

Output Post Processor (OPP) in oracle R12

What is Output Post Processor?

Concurrent Processing now uses the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests.Post-processing actions are actions taken on concurrent request output. An example of a post-processing action is that used in Concurrent Processing support of XML Publisher.
If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

OPP runs as a service that can be managed through Oracle Applications Manager (OAM) from the System Activity page (Navigation: Applications Dashboard > Applications

Service (from the dropdown list) > Go).

The integration of XML Publisher within Concurrent Processing is done by means of a specialized concurrent manager called the Output Post Processor (OPP). If a request is submitted which has an XML Publisher template specified as a layout for the output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

An overview of the actions involved:

1. An application user submits an XML Publisher based report.
2. The standard concurrent manager processes the request.
3. The XML data file is generated by the standard concurrent manager. This can be done by various methods:
o Oracle Reports - Report Definition File (RDF)
o XML Publisher Data Template - XML data template linked to the Data Definition
o Any other process that produces XML output
4. A post processing action defines that the output needs to be generated by the Output Post Processor hence it is triggered by the standard manager.
5. The Output Post Processor generates the final report and informs the standard concurrent manager whether that was successful.
6. The standard concurrent manager finalizes the concurrent request.

Processes in OPP:


There should always be at least one OPP process active in the system. If no OPP service is available to process concurrent requests, completed requests that require OPP post-processing will complete with a status of Warning.

One service instance of the OPP service is seeded by default. This seeded OPP service instance has one workshift with one process.

 A concurrent manager contacts an available OPP process when a running concurrent request needs an OPP post-processing action. Concurrent managers use a local OPP process (on the same node) by default, but will choose a remote OPP if no local OPP process is available.


How to Increase the number of Output Post Processors?
1.Log on to Applications with “System Administrator” responsibility.
2.Navigate to Concurrent -> Manager -> Define.
3.Query for the “Output Post Processor” service.
4.Click on “Work Shifts” and increase the number of processes

How to get OPP manager log file location?

$APPLCSF/log/<SID>/FNDOPP####.txt       OR
1,System Administrator > Concurrent > Manager > Administer
2,Search for ‘Output Post Processor’
3,Click the ‘Processes’ button .
4,Click the Manager Log button. This will open the ‘OPP’
Upload the OPP log file.

In some cases, Output Post Processor is not start up and it shows Actual and Target are showing different values when we query for Output Post Processor.
The log files shows that no error message.In this case apply the following possible solution for starting the OPP.


1. Shutdown the internal manager by using adcmctl.sh stop apps/apps
2. Make sure there is no FNDLIBR processe running:
$ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR
3. If there is any FNDLIBR processe please kill it $ kill -9 pid
4. Run cmclean.sql script as document from Note 134007.1
5. Restart the internal manager by using adcmctl.sh start apps/apps

or

How to kill and start Output Post Processor (OPP) Background:

This article explains how to kill OPP and restart the same

Solution:
1,System Administator > Concurrent > Manager > Administer
2,Query "Output Post Processor" -> Processes button
Get the sytem id of "Output Post Processor"
3,ps -ef|grep [system id]
4,kill -9 [system id] in Unix
5,System Administator > Concurrent > Manager > Administer
6,Query "Output Post Processor" -> Restart button

Output Post Processor (OPP) in oracle R12

What is Output Post Processor?

Concurrent Processing now uses the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests.Post-processing actions are actions taken on concurrent request output. An example of a post-processing action is that used in Concurrent Processing support of XML Publisher.
If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

OPP runs as a service that can be managed through Oracle Applications Manager (OAM) from the System Activity page (Navigation: Applications Dashboard > Applications

Service (from the dropdown list) > Go).

The integration of XML Publisher within Concurrent Processing is done by means of a specialized concurrent manager called the Output Post Processor (OPP). If a request is submitted which has an XML Publisher template specified as a layout for the output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output.

An overview of the actions involved:

1. An application user submits an XML Publisher based report.
2. The standard concurrent manager processes the request.
3. The XML data file is generated by the standard concurrent manager. This can be done by various methods:
o Oracle Reports - Report Definition File (RDF)
o XML Publisher Data Template - XML data template linked to the Data Definition
o Any other process that produces XML output
4. A post processing action defines that the output needs to be generated by the Output Post Processor hence it is triggered by the standard manager.
5. The Output Post Processor generates the final report and informs the standard concurrent manager whether that was successful.
6. The standard concurrent manager finalizes the concurrent request.

Processes in OPP:


There should always be at least one OPP process active in the system. If no OPP service is available to process concurrent requests, completed requests that require OPP post-processing will complete with a status of Warning.

One service instance of the OPP service is seeded by default. This seeded OPP service instance has one workshift with one process.

 A concurrent manager contacts an available OPP process when a running concurrent request needs an OPP post-processing action. Concurrent managers use a local OPP process (on the same node) by default, but will choose a remote OPP if no local OPP process is available.


How to Increase the number of Output Post Processors?
1.Log on to Applications with “System Administrator” responsibility.
2.Navigate to Concurrent -> Manager -> Define.
3.Query for the “Output Post Processor” service.
4.Click on “Work Shifts” and increase the number of processes

How to get OPP manager log file location?

$APPLCSF/log/<SID>/FNDOPP####.txt       OR
1,System Administrator > Concurrent > Manager > Administer
2,Search for ‘Output Post Processor’
3,Click the ‘Processes’ button .
4,Click the Manager Log button. This will open the ‘OPP’
Upload the OPP log file.

In some cases, Output Post Processor is not start up and it shows Actual and Target are showing different values when we query for Output Post Processor.
The log files shows that no error message.In this case apply the following possible solution for starting the OPP.


1. Shutdown the internal manager by using adcmctl.sh stop apps/apps
2. Make sure there is no FNDLIBR processe running:
$ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR
3. If there is any FNDLIBR processe please kill it $ kill -9 pid
4. Run cmclean.sql script as document from Note 134007.1
5. Restart the internal manager by using adcmctl.sh start apps/apps

or

How to kill and start Output Post Processor (OPP) Background:

This article explains how to kill OPP and restart the same

Solution:
1,System Administator > Concurrent > Manager > Administer
2,Query "Output Post Processor" -> Processes button
Get the sytem id of "Output Post Processor"
3,ps -ef|grep [system id]
4,kill -9 [system id] in Unix
5,System Administator > Concurrent > Manager > Administer
6,Query "Output Post Processor" -> Restart button

The concurrent manager has timed out waiting for the Output Post-processor to finish this request.

The concurrent manager has timed out waiting for the Output Post-processor to finish this request.

Check that there are enough Output Post-processor service processes running.

More information may be found in the service process logfile.

Output Post Processor (OPP) issue



Solution:

Two profiles options actually control the timeouts of OPP.

             i.        Concurrent:OPP Response Timeout
            ii.        Concurrent:OPP Process Timeout

  1. OPP No Response: 
                      i.        Increase the value (in seconds) for the profile option 'Concurrent:OPP Response Timeout'. If the current value is 120 then set it to 7200. 
                     ii.        Increase the number of processes or threads (or both) of the OPP via System Administrator >Profile>
Find Both like that or set value 7200..
 %Concurrent%OPP%Process%Timeout%
7200
%Concurrent%OPP%Response%Timeout%
7200

Save it.

                    iii.        Bounce application services.

Wednesday, 7 September 2016

REP-0004 INVOKING THE ORACLE REPORTS BUILDER

REP-0004 INVOKING THE ORACLE REPORTS BUILDER (Doc ID 1013620.6)

APPLIES TO:

Oracle Reports Developer - Version 6.0 to 11.1.2.2.0 [Release 6 to 11g]
Oracle Application Object Library - Version 11.0.0 to 12.1 [Release 11 to 12.1]
Generic UNIX
Checked for relevance on 20-Oct-2015

SYMPTOMS

You are receiving the following error from Oracle Reports:

REP-0004 : Warning - Unable to open user preference file.

 There may also be other errors like:

REP-0003  - Warning - Unable to open global preference file.

REP-3000 - Internal error starting Oracle Toolkit.

CAUSE

 There are several causes of this error.

SOLUTION

Possible causes and solutions of REP-0004 include the following:

1.  No prefs.ora file in HOME directory:

Oracle Reports will look into the user's HOME directory for the prefs.ora preferences file.
 If a prefs.ora file does not exist in your HOME directory, you can copy the prefs.ora
file that came with the Oracle Tools.

A prefs.ora file is shipped with the Oracle Tools, and is located in:

$ORACLE_HOME/tools/admin/prefs.ora

You can also create a prefs.ora file the first time you are in the Reports Builder

To create a prefs.ora file from the Oracle Reports Builder

Oracle Reports 6.0.X:

Start the Oracle Reports Builder
Select Tools->Preferences
Select your preferences
Press the OK button
This will save a prefs.ora file in your HOME directory when you exit Reports Builder.
Oracle Reports 9.x / 10.x /11.x:

Start the Oracle Reports Builder
Select Edit->Preferences
Select your preferences
Press the OK button
This will save a prefs.ora file in your HOME directory when you exit Reports Builder.

2.  Location of the prefs.ora file:

If you want to use a prefs.ora file in a different directory than HOME (for versions < 11g) or
ORACLE_INSTANCE/config/FRComponent/frcommon/tools/admin/ for 11g, set the
 $ORACLE_LOCALPREFERENCE environment variable to that directory.

Example:  You want all users to access a common prefs.ora file located in /home/allusers/prefs.ora.

% setenv ORACLE_LOCALPREFERENCE /home/allusers

              OR

% export ORACLE_LOCALPREFERENCE=/home/allusers

3.  Insufficient privileges on the prefs.ora file:

The user invoking Oracle Reports must have read privileges on the prefs.ora file.  

4.  A system error made it impossible to open the file. 

The preferences file may have become corrupted.  If you suspect file corruption,
copy $ORACLE_HOME/tools/admin/prefs.ora and respecify your preferences.  

Note:
Oracle Forms and Oracle Graphics also read prefs.ora, thus you will have to respecify
all preferences that were set in the corrupted prefs.ora file.
Consult your operating system documentation or contact your system administrator for assistance
 setting environment variables or file privileges.

REP-0004

REP-0004: Warning: Unable to open user preference file

Metalink id:
R12: Request Logs Contain the Message "REP-0004: Warning: Unable to open user preference file" [ID 1120529.1]


Symptoms:

All concurrent requests that run REPORTS are printing the following warning in the request log.
REP-0004: Warning: Unable to open user preference file.

Cause:

This message occurs when the concurrent process attempts to open the Oracle Reports executable and your local preference file cannot be found or opened. This is just a warning, so the request will continue to run even if this occurs.

Solution:

To resolve the warning, copy the prefs.ora file from your Reports Builder $ORACLE_HOME/tools/admin/ directory into the Applications $HOME directory.

Example:

Copy of the file prefs.ora in the directory /apps/prod/apps/tech_st/10.1.2/tools/admin/ to the directory  /home/applprod/.

[applprod@sujeet ~]$ cd /apps/prod/apps/tech_st/10.1.2/tools/admin/

[applprod@sujeet  admin]$ ls
prefs.ora  

[applprod@sujeet  admin]$ cp prefs.ora /home/applprod/

Note: Bounce apache service.



Issue resolved.


NOTE:
For a report developed by xml publisher getting the same error, create /HDDATA/xml_tmp directory (environment dependent) on the system server after checking Administration from XML Publisher Administrator responsibility -> Configuration -> General -> Temporary directory column is /HDDATA/xml_tmp.

Friday, 2 September 2016

APP-FND-00362

"APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM,
 because the environment variable &BASEPATH is not set for the application to
which the concurrent program executable &EXECUTABLE belongs."


Cause :- 

The issue is caused by a custom executable name for the Invoice on Hold report: XXX_APXINROH


Solution :-

(R) : System Administrator
(N) : Concurrent > Program > Define

Search for short name : APXINROH
1 - Change the Executable Name from XXX_APXINROH to APXINROH
2 - Re-run the report and confirm the error is resolved.

If issue not resolved please try below steps.

OR

The error occurs when run only Thai Localization Reports.
And your customer confirms, the issue was solved after setting the basepath of $CLA_TOP in .env file.

Thursday, 1 September 2016

Linux 7 installation steps

 Red Hat Enterprise Linux 7 (64 bit) Installation steps by steps

Once you insert and boot your machine with the RHEL DVD, you will get the below screen. 

Select "Install Red Hat Enterprise Linux 7 and Press "Enter".

Select the Language preference.

The Next screen contains almost all the configuration which has to be performed for the installation. Since we have already selected our Language and Keyboard preferences, we can skip that step here.

Lets start by setting the Date and Time.

Select your Location as for me it is Asia/Kolkata.

Next we will select the packages which we want to install. So Select "Software Installation" which will lead you to the below screen. In my case I will install the "Base Installation" package having "Server with GUI" and in case you want to add any extra Add On, you can select the same from the left panel as shown below.

Next we need to configure partitions. So select "Installation Destination"

Select the hard disk which you have used to install RHEL 7, as for my case as you can see 200 GB hard drive.

Also if you want the OS to automatically create the partition select the same or else for this article lets manually create the partitions.

I will create /boot/swap space 
note- swap space depend on RAM size if RAM-10 GB than Swap-20 GB.

Click on Done and select Accept Changes.

The last one is to Configure Network.

Change the Ethernet device name or else you can skip that part. Next configure you IP details as per your environment i.e IPv4 or IPv6. We are using IPv4 so selected the "IPv4 Settings" and added the IPNetmask,Gateway and DNS details in the same.. Click on "Done" to save the configuration and go a step back.

So we are done here with all the options on this screen. Next we can "Begin Installation"

As you see the installation has begun in the mean time you can add a password for your root user. Also you can create additional user by using the "User Creation" thumbnail.

Provide a password for root account.

Create a user.(Optional).

In the mean time let the installation complete. Once done click on Reboot.

Once the machine reboots, next it will prompt the below screen. Click on "License Information"

Accept the Terms and Conditions.

Click on "Finish Configuration".

Next you will get the Kdump configuration page.

Let us enable the Kdump and let the machine decide the amount of memory required for the same.

I do not want to register my system to RHN as for now,also we can perform this step later so let us skip this part for now.

Next you get your Login Screen which means we have successfully installed our Operation System i.e. RHEL 7.0 (64 bit).