Content Server : Unable to retrieve root IdcAdmin page. Permission denied. Address '127.0.0.1' is not an allowable remote socket address.

This blog is to know about where to start the Content Server.

When you click Content Server Admin from Login Page of Content Server, the error message like:

The Issue:
Unable to retrieve root IdcAdmin page. Permission denied. Address '127.0.0.1' is not an allowable remote socket address.

Check the config.cfg in /CS_dir/config for like
SocketHostAddressSecurityFilter=127.0.0.1 (Be sure to have the entry like this)


It has two servers. The executables are like

1. /CS_dir/etc/idcadmin_start / idcadmin_restart
2. /CS_dir/admin/etc/idcadmin_start /idcadmin_restart

Start the Services using the second one.

It will be fix to your Issue.

Cheers!!!

Oracle Content Server - Issues 1

Today, I faced a critical error, that needs to be blogged out.

When I changed some parameter after Installation of Oracle Content Server, i need to restart the Content Server Services

When i tried with /CS_dir/etc/idcserver_start

i received message like

[oracle@earth etc]$ ./idcserver_start
Starting the Content Server idc... The server terminated unexpectedly.
'CheckoutAndOpenInNative' component, version '2008-06-17', extends checkoutandopeninnative feature(s)
'ContentFolios' component, version '1.0.0.87 ($Rev: 65280 $)', extends Folios:1.0.0-1.0.0.87 feature(s)
'ConfigMigrationUtility' component, version '2008_07_01 (build 51)', extends ConfigurationMigration:1.0-1.0.0.51 feature(s)
'FileStoreProvider' component, version '2008_05_21 (build 17)', extends FileStoreProvider feature(s)
'Folders_g' component, version '2008_07_25 (build 24) ($Rev: 65025 $)', extends folders:7.2-1000.0.0.24 feature(s)
'Helper' component, version '6.2 20080410T1355', extends Helper:6.2-0.0.558.1215716087 feature(s)
'InboundRefinerySupport' component, version '2008_07_16 (build 22)', extends Inbound Refinery:8.1.0.0 feature(s)
'CoreWebdav' component, version '2008_05_27 (build 17)', extends webdav:2.0-2.0 feature(s)
'FCKEditor' component, version '2007_06_19 (build 7)', extends FckEditor feature(s)
'NativeOsUtils' component, version '080222 (build $Rev: 61118 $)', extends NativeOsUtils feature(s)
'ContentAccess-linux' component, version '080222 (build $Rev: 64037 $)', extends ContentAccess:10gR3-8.1.9 feature(s)
'ComponentTool' component, version '080710 10gR3 (build $Rev: 64602 $)', extends ComponentTool feature(s)
'CoreUserInterfaceLibrary' component, version '2008_07_30 ($Rev: 65084 $)', extends CoreUserInterfaceLibrary feature(s)
'PopUpCalendar' component, version '2008_06_24 ($Rev: 64134 $)', extends PopUpCalendar feature(s)
'YahooUserInterfaceLibrary' component, version '2008_08_05 ($Rev: 65289 $)', extends YahooUserInterfaceLibrary feature(s)
'iTextComponent' component, version '2007_10_15 (build 2) ($Rev: 56511 $)', extends iTextComponent:2.0-1.0.0.2 feature(s)
Failed to initialize the server.
(internal) 04.13 13:37:47.927 main !csFailedToInitServer (!csDbUnableToPerformAction_create,ManagedLinks!$ORA-00955: name is already used by an existing object
)-exception stack
intradoc.common.ServiceException: !csDbUnableToPerformAction_create,ManagedLinks!$ORA-00955: name is already used by an existing object

at intradoc.server.IdcServerManager.init(IdcServerManager.java:148)
at IdcServer.init(IdcServer.java:64)
at IdcServer.main(IdcServer.java:37)
Caused by: intradoc.data.DataException: !csDbUnableToPerformAction_create,ManagedLinks!$ORA-00955: name is already used by an existing object

at intradoc.jdbc.JdbcWorkspace.createTable(JdbcWorkspace.java:1446)
at intradoc.server.IdcExtendedLoader.createTable(IdcExtendedLoader.java:2682)
at linkmanager.LinkManagerInstallFilter.linkManageUpgrade(LinkManagerInstallFilter.java:92)
at linkmanager.LinkManagerInstallFilter.doFilter(LinkManagerInstallFilter.java:54)
at intradoc.shared.PluginFilters.filter(PluginFilters.java:92)
at intradoc.server.IdcExtendedLoader.executeFilter(IdcExtendedLoader.java:285)
at intradoc.server.IdcExtendedLoader.extraBeforeCacheLoadInit(IdcExtendedLoader.java:255)
at intradoc.server.IdcSystemLoader.loadCaches(IdcSystemLoader.java:928)
at intradoc.server.IdcServerManager.init(IdcServerManager.java:79)
... 2 more
Caused by: java.sql.SQLException: ORA-00955: name is already used by an existing object

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190)
at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1657)
at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1626)
at intradoc.jdbc.JdbcFunctions.executeUpdateQuery(JdbcFunctions.java:1162)
at intradoc.jdbc.JdbcFunctions.executeCreateTableQuery(JdbcFunctions.java:1068)
at intradoc.jdbc.JdbcWorkspace.createTable(JdbcWorkspace.java:1433)
... 10 more
Unable to create table 'ManagedLinks'. ORA-00955: name is already used by an existing object
ORA-00955: name is already used by an existing object

intradoc.common.ServiceException: !csDbUnableToPerformAction_create,ManagedLinks!$ORA-00955: name is already used by an existing object

at intradoc.server.IdcServerManager.init(IdcServerManager.java:148)
at IdcServer.init(IdcServer.java:64)
at IdcServer.main(IdcServer.java:37)
Caused by: intradoc.data.DataException: !csDbUnableToPerformAction_create,ManagedLinks!$ORA-00955: name is already used by an existing object

at intradoc.jdbc.JdbcWorkspace.createTable(JdbcWorkspace.java:1446)
at intradoc.server.IdcExtendedLoader.createTable(IdcExtendedLoader.java:2682)
at linkmanager.LinkManagerInstallFilter.linkManageUpgrade(LinkManagerInstallFilter.java:92)
at linkmanager.LinkManagerInstallFilter.doFilter(LinkManagerInstallFilter.java:54)
at intradoc.shared.PluginFilters.filter(PluginFilters.java:92)
at intradoc.server.IdcExtendedLoader.executeFilter(IdcExtendedLoader.java:285)
at intradoc.server.IdcExtendedLoader.extraBeforeCacheLoadInit(IdcExtendedLoader.java:255)
at intradoc.server.IdcSystemLoader.loadCaches(IdcSystemLoader.java:928)
at intradoc.server.IdcServerManager.init(IdcServerManager.java:79)
... 2 more
Caused by: java.sql.SQLException: ORA-00955: name is already used by an existing object

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190)
at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1657)
at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1626)
at intradoc.jdbc.JdbcFunctions.executeUpdateQuery(JdbcFunctions.java:1162)
at intradoc.jdbc.JdbcFunctions.executeCreateTableQuery(JdbcFunctions.java:1068)
at intradoc.jdbc.JdbcWorkspace.createTable(JdbcWorkspace.java:1433)
... 10 more


Fix:

Goto

/CS-dir/bin/ComponentWizard

Select LinkManager8

1. Disble LinkManager8 (if you have installed, then you could face this issue)
2. Uninstall LinkManager8

then Start the CS Services

CS-dir/etc/idcserver_start

Starting the Content Server idc ... Success: Process 15705

Cheers!!!

Keep on observing this Thread.. Still lot to come on Content Server

Configuring OLM in Oracle Apps 12.1.1

Hi, Today i need to blog out the experience in integrating OLM documents into oracle apps.

First of all place the CD containing the Course material into a mount point.

It should have the following structure:
index.html, related files like
D__/
autorun.inf*
common/
index.html*
logon/
lost+found/
shellexecute.exe*
Company_ethics/
version.txt*

Now, configure the httpd.conf in $WEB_ORACLE_HOME/Apache/Apache/conf

add the following lines at the end of httpd.conf

Alias /doc_documentation/ "/doc_documentation/"

## Options FollowSymLinks MultiViews
AllowOverride None
#mwit start
Order allow,deny
Allow from all


once this lines are added, please bounce the middle tier services.

then When i try to login to the URL

http://servername:8000/doc_documentation

it showed,

Location /doc_documentation is not found in the server

Then, i tried looking into the error_log from $LOG_HOME/ora/10.1.3/Apache

i found that, the directory has to be stored in the location of portal directory as below:
[Tue Feb 23 13:09:34 2010] [error] [client 43.88.68.84] [ecid: 1266926974:172.24.130.118:831724:0:5,0] File does not exist: /oracle/SID/inst/apps/SID_host/portal/doc_documentation/

I created a soft link to this location from where i created the directory.

When i access the URL, wow, it worked with all the features.

Here are the example:

Issues and Fixes with OBIEE

For Installation of the OBIEE please follow my previous post http://balajiabhi.blogspot.com/2009/07/installation-and-configuration-of-obiee.html


Issue:
The login page failed to login using Administrator/Administrator
Fix:
1. Shutdown the oc4j using
$(ORACLE_BI_HOME)/setup/oc4j

oc4j will give the options like
-start
-shutdown -port (ORMI Port) -password (Password which you gave during the installation) for oc4jadmin

ORMI Port:
Locate rmi.xml in the
$ORACLE_BI_HOME/oc4j_bi/j2ee/home/config/rmi.xml
Inside you can get the port of the ORMI Port.
In my case it was 23971
I stopped oc4j
like

ORACLE_BI_HOME/setup/oc4j -shutdown -port 23971 -password Welcome1
Shutdown OC4J instance...

The locate the xmlp-server-config.xml inside
$ORACLE_BI_HOME/ xmlp/ XMLP/ Admin/ Configuration /xmlp-server-config.xml

Change the variableproperty name=”SECURITY_MODEL” value=”BI_SERVER“/
TO
property name=”SECURITY_MODEL” value=”XDO“/
3. Restart the oc4j from
$ORACLE_BI_HOME/setup/oc4j -start
Now the Administrator/Administrator will work
You can now navigate to Admin page from welcome page.

Issue 2:
When you access the Dashboard from the OBIEE Page, you may encounter

500 Internal Error: - servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.

I resolved the issue like this:
1. Edit ./oc4j_bi/j2ee/home/applications/analytics/analytics/WEB-INF/web.xml

Replace the port as 9703 instead of 9710

2. Go to $ORACLE_BI_HOME/setup/

$run-sa.sh stop

wait for 10 seconds

$run-saw.sh stop

wait for 10 seconds

$run-sa.sh start

$run-saw.sh start.

Now click on the application Dashboard. It will work fine.

Installation and Configuration of OBIEE 10.1.3.4.1

The Blog is about installation and Configuration of OBIEE 10.1.3.4 (Basic Installation)

You can obtain OBIEE here

The Prerequisites:
1. JDK1.5.0 or above Download JDK

A Server with temporary tablespace of around 200 MB

Considerations:
The Document follows the installation procedure on RHEL 4 update 5

1. Unzip the biee_linux_x86_redhat_101341.zip
2. It will deploy
about.jsp
biee_linux_x86_redhat_101341_1of1.tar
META-INF
WEN-INF

3. untar the biee_linux_x86_101341_1of1.tar using
$tar -xvf biee_linux_x86_101341_1of1.tar

4. It will create RH_LINUX
Run: Server/Oracle_Business_Intelligence/setup.sh

You follow the screens, and specify the necessary informations

5. Follow the install log located in
$ORACLE_BI_HOME/log/install.log

Once completed you will be given an output stating to browse the html page in the location of Oracle BI HOME

Start working using
http://hostname:port (port will be 9704)/xmlpserver

Issue:
The login page failed to login using Administrator/Administrator
1. Shutdown the oc4j using
$(ORACLE_BI_HOME)/setup/oc4j

oc4j will give the options like
-start
-shutdown -port (ORMI Port) -password (Password which you gave during the installation) for oc4jadmin

ORMI Port:
Locate rmi.xml in the
$ORACLE_BI_HOME/oc4j_bi/j2ee/home/config/rmi.xml
Inside you can get the port of the ORMI Port. In my case it is 23971

I stopped oc4j like
ORACLE_BI_HOME/setup/oc4j -shutdown -port 23971 -password Welcome1
Shutdown OC4J instance...

The locate the xmlp-server-config.xml inside
$ORACLE_BI_HOME/ xmlp/ XMLP/ Admin/ Configuration /xmlp-server-config.xml

Change the variable
property name=”SECURITY_MODEL” value=”BI_SERVER“/
TO
property name=”SECURITY_MODEL” value=”XDO“/

3. Restart the oc4j from
$ORACLE_BI_HOME/setup/oc4j -start

Now the Administrator/Administrator will work

You can now navigate to Admin page from welcome page.

Issues:

When you access the Dashboard from the OBIEE Page, you may encounter

500 Internal Error: - Server error: An exception occured. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.

I resolved the issue like this:

1. Edit ./oc4j_bi/j2ee/home/applications/analytics/analytics/WEB-INF/web.xml

Replace the port as 9703 instead of 9710

2. Go to $ORACLE_BI_HOME/setup/

$run-sa.sh stop

wait for 10 seconds

$run-saw.sh stop

wait for 10 seconds

$run-sa.sh start

$run-saw.sh start.

Now click on the application Dashboard. It will work fine.

Oracle Beehive and Beekeeper Installation

I need to blog out my experience with Oracle Beehive 1.5 Installation and Beekeeper installation.
Download the oracle beehive and beekeeper from here
The Prerequisites:
It is better to choose a linux box with new install. If it has prior opmn instance running... then it will spoil your days.
Supported OS:

Oracle Beehive supports the following Linux (x86 32-bit or x64 in 32-bit shell mode) operating system certifications:

• Oracle Enterprise Linux 4

• Oracle Enterprise Linux 5

• Red Hat Enterprise Linux 4 Update 3 and later

• Red Hat Enterprise Linux 5




• SUSE Linux Enterprise 9.0 with Service Pack 2 and later

• SUSE Linux Enterprise 10.0

Kernel Version:

The system must be running the following kernel version (or a later version):

• Red Hat Enterprises Linux 4 and 5: 2.6.9-29.EL

I Used Redhat EL 4 update 5 (Nanhant October)

Required Kernel Parameters:

If the value of any kernel parameter is different from the minimum value, then complete the following procedure:

1. Using any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following:

   net.ipv4.ip_local_port_range = 22000 65000
   
   

   
   
   
   

   By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system. However, on SUSE Linux Enterprise Server systems, enter the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:

   # /sbin/chkconfig boot.sysctl on

2. Enter the following command to change the current values of the kernel parameters:

   # /sbin/sysctl -p
   

   
   
   
   

   Review the output from this command to verify that the values are correct. If the values are incorrect, edit the /etc/sysctl.conf file, then enter this command again.

3. Enter the command /sbin/sysctl -a to confirm that the values are set correctly.

After updating the values of kernel parameters in the /etc/sysctl.conf file, either restart the computer, or run the command /sbin/sysctl -p to make the changes in the /etc/sysctl.conf file available in the active kernel memory.

OS Packages (Important)

• Oracle Enterprise Linux 4 and Red Hat Enterprise Linux 4

  • gcc-3.4.5-2 (GNU Compiler Collection)

  • gcc-c++-3.4.5-2 (C++ support for GCC)

  • openmotif21-2.1.30-11.RHEL4.4 (Open Motif run time libraries and executables)

  • setarch-1.6-1 (Personality setter)

  • pdksh-5.2.14-30.3 (Public domain Korn shell)

  • sysstat-5.0.5-7 (System monitoring commands sar and iostat)

  
  

  • gnome-libs-1:1.4.1.2.90-44.1 (GNOME basic libraries)
    

  • libstdc++-3.4.5-2 (GNU Standard C++ Library)

  
  

  • libstdc++-devel-3.4.5-2 (Header files and libraries for C++ development)

  
  

  • compat-libstdc++-296-2.96-132.7.2 (Compatibility 2.96-Red Hat standard C++ libraries)
    

  • compat-db-4.1.25-9 (Berkeley DB database library for Red Hat Linux 7.x compatibility)

  • control-center-2.8.0-12rhel4.2 (GNOME Control Center)

  • glibc-common-2.3.4-2.9 (Common binaries and locale data for glibc)
    
    binutils-2.15.92.0.2-18 (GNU Binary Utility Development Utilities)

  • make-1:3.80-5 (GNU make)

  • xscreensaver-4.18-5.rhel4.10 (X Window System screen saver and locker)

  • xorg-x11-deprecated-libs-6.8.2-1.EL.13.25 (Deprecated X Window System shared libraries)

Increase the Shell Limits:

1. Add the following lines to the /etc/security/limits.conf file:

   oracle              soft    nproc   2047
   
   oracle              hard    nproc   16384
   
   oracle              soft    nofile  1024
   
   oracle              hard    nofile  65536




2. Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:

   session  required  /lib/security/pam_limits.so
   
   

Oracle Enterprise Manager Grid Control Requirements

If you want to install the Oracle Beehive Provisioning Application, which enables you to install Oracle Beehive from Oracle Enterprise Manager Grid Control, you must have Oracle Enterprise Manager 10g Release 4 Grid Control (10.2.0.4) or later.
Hardware Requirements

The following are the minimum hardware requirements for Oracle Beehive:

• Disk Space: 2.6 GB


• Swap Space: 2,048 MB



• Memory:

  • Oracle Beehive: 2 GB RAM

  • Oracle Beehive for DMZ: 1 GB

Oracle Database Requirements:
I had 10.2.0.1 Database. I installed 10.2.0.1 and upgraded to 10.2.0.4 using the patchset. Then applied the patches for 10.2.0.4: The patches are as follows:

Patches(Opatch on 10.2.0.4)

6369463: WRONG RESULTS WHEN USING ORA_ROWSCN PSEUDOCOLUMN
4033868: COLLECT FUNCTION LEAVES TEMPORARY SYS TYPES BEHIND
6653934: XF11.1SSHR - TRC - KDRWRIC
6725634: STBH SYNONYMS ARE INVALIDATED WHEN A TABLE PARTITION IS DROPPED
6897966: JOBS AREN'T STARTED SERVICE NAME IS CASE SENSITIVE
6923450: ORA-07445 [KOTGTSCH] - AFTER UPGRADE TO 10.2.0.4
6600258: DBMS_CDC_SUBSCRIBE.EXTEND_WINDOW THROWS ORA-31462
6145687: BETA4:VERY STRANGE SYSTEM CHANGE NUMBER

Initialization Parameters:

java_pool_size = 50M (52428800)
job_queue_processes = 10
processes = 150
streams_pool_size 100M If your SGA (System Global Area) of the database is large (more than 3G), then set this parameter to 200M.
undo_retention = 3600

Important: While creation of Database you enable the Archivelog and the Characterset of the Database should be AL32UTF8

Beehive Installation

Explanation of the sequence of screens

from the Unzipped location: run ./runInstaller

Welcome
This screen welcomes you to the Oracle Install Wizard. It will guide you through the installation and configuration of Oracle Beehive Release 1.
The following describes the buttons that appear on most of the installation screens:
Click Help to view the online help.
Click Save to save the inputs you have entered to a file that you can use later as a response file. You can use this response file to continue the installation at a later time or perform a silent (non-interactive) installation.

Click Back to go back to the previous step.
Click Next to go to the next step.
Click Install to start the installation of the product.
This button is available only on the Summary screen.
Click Uninstall to uninstall a previously installed Oracle Beehive product
Click Cancel to exit from the Oracle Install Wizard at any time during the installation.

New Inventory Location
If Oracle Beehive Release 1 is the first Oracle product you are installing on a computer, then this screen is displayed.
On this screen, you specify in the Inventory Directory Path field the location of an inventory directory (the oraInventory directory). The Oracle Beehive Install Wizard will use this inventory directory to keep track of all Oracle products installed on the computer.

Specifying Oracle Home Directory on Linux and UNIX-Based Systems
On Linux and UNIX-based systems, the Oracle Beehive Install Wizard suggests a path similar to the following for the Oracle home directory:/home_directory/oracle/product/version_number/identifier_n

My machine:

/oracle/BEEHIVE1/product/1.5.0/beehive_1

Prerequisite Checks
This screen displays the prerequisite checks that the Oracle Beehive Install Wizard runs. It verifies that the host (where you are installing Oracle Beehive Release 1) meets all minimum requirements for installing and configuring the product type.

Some of the platform-independent checks that the Oracle Beehive Install Wizard performs include:
Operating system certification (or version)
Operating system patches and packages
Security kernel parameters
Memory
Swap space
Disk space
If an automatic check fails, fix it and click Retry.

This will install the software packages in the newly created Beehive Home.

It will be installed and configured. (if you choose Install and configure). Else you should start from $BEEHIVE_HOME/beehive_1/beehive/oobwiz/.

Address the issues if you face during installation. ( I faced so many errors in plsql code as well as in the java properties and xml)

Later after installation, you will get the installation os successful. But you will not get the port no to access. You have to deploy beekeeper over beehive installation. Select new oracle home for installing beekeeper. This install will give you the portal page to access.

http://beehive.chainsys.com:7779/bkpr is the URL of my instance.

Later you have to login using beeadmin and password you gave during installation. I selected Welcome1 as the universal password. Because it requires lot of passwords to be remembered :)

Starting

To start all Oracle Beehive managed components using the beectl command-line utility, use the start command with the --all option.

The following example illustrates the command with the --all option, as well as the resulting output:

beectl> start --all
Starting all the beehive components ...
Successfully started all the beehive components.
Operation completed in .

Stopping

To stop all Oracle Beehive managed components using the beectl command-line utility, use the stop command with the --all option.

The following example illustrates the command with the --all option, as well as the resulting output:

beectl> stop --all
Stopping all the beehive components ...
Successfully stopped all the beehive components.
Operation completed in .

Restarting

To restart all Oracle Beehive managed components using the beectl command-line utility, use the restart command with the --all option.

The following example illustrates the command with the --all option, as well as the resulting output:

beectl> restart --all
Stopping all the beehive components ...
Successfully stopped all the beehive components.
Operation completed in .

Starting all the beehive components ...
Successfully started all the beehive components.
Operation completed in .

Determine the component identifiers of all managed components by running the status command:

beectl> status
--------------------------------------------+----------------+---------------
Component identifier                        | Component type | Status
--------------------------------------------+----------------+---------------
BTI_redirector_instance1.host.domain.com    | Bti            | RUNNING
--------------------------------------------+----------------+---------------
BEECLIENT_instance1.host.domain.com         | ManagedOc4j    | RUNNING
--------------------------------------------+----------------+---------------
BEEAPP_instance1.host.domain.com            | ManagedOc4j    | RUNNING
--------------------------------------------+----------------+---------------
BEEMGMT_instance1.host.domain.com           | ManagedOc4j    | RUNNING
--------------------------------------------+----------------+---------------
BEECORE_instance1.host.domain.com           | ManagedOc4j    | RUNNING
--------------------------------------------+----------------+---------------
oc4j_soa_instance1.host.domain.com          | ManagedOc4j    | RUNNING
--------------------------------------------+----------------+---------------
ohs_instance1.host.domain.com               | HttpServer     | RUNNING
--------------------------------------------+----------------+---------------

Beekeeper Restart process:

Oracle Beekeeper is installed as a separate, stand-alone OC4J process. To start or stop Oracle Beekeeper, you start or stop the OC4J component, by using the opmnctl utility.

Ensure your environment is set with the following variables. Adjust the variables to match the install path and version numbers appropriate to your particular installation:

ORACLE_HOME,ORACLE_BASE
PATH=$PATH:$ORACLE_HOME/opmn/bin

To start Oracle Beekeeper, perform the following steps:

1. From the command line on the machine where Oracle Beekeeper is installed, start opmnctl:

   > opmnctl start
   opmnctl: opmn started.
   

2. Check the status of the OC4J process:

   > opmnctl status
   

   You should see output similar to the following:

   Processes in Instance: BeehiveControl
   ---------------+--------------+-----+---------
   ias-component | process-type  | pid | status
   ---------------+--------------+-----+---------
   bkpr           | bkpr         | N/A | Down
   

3. Start Oracle Beekeeper:

   > opmnctl startproc process-type=bkpr
   opmnctl: starting opmn managed processes...
   

To stop Oracle Beekeeper, perform the following steps:

1. From the command line on the machine where Oracle Beekeeper is installed, run the following command:

   > opmnctl stopproc process-type=bkpr
   opmnctl: stopping opmn managed processes...
   

2. If you want to, you can also stop opmnctl:

   > opmnctl stopall
   opmnctl: stopping opmn and all managed processes...

Thats all.. cheers!!!

Integrating Apex 3.2 with R12 (With Oracle Application Server 10g on the other Machine)

Today, I need to blog out my experience with Apex integration with R12 E Business Suite!!!

How I did: as follows.

As you know how to install Oracle Application Server 10.1.2.0 (Database 10.1.0.4)

1. Download Application Server 10g from OTN
2. Unzip the content. It will create 4 Disks (Disk1, Disk2, Disk3 and Disk4)

3. From Disk1 run
$./runInstaller

This will bring up the welcome screen. Select the Oracle home and other requisites. Later,
Select to Oracle Application Server Infrastructure 10g (10.1.2.0.2)

It will create one new database, (10g, Version 10.1.0.4) and New OID, Oracle Application server single-sing on, metadata repository and others. (I will detailedly explain how we can configure Application server in a separate blog)

Finish the installation. This will bring you basic HTTP server (OHS managed by OPMN)

This is what we want right at the moment.

Write a profile for database as follows.
export ORACLE_HOME=/oracle/ASHOME/
export ORACLE_SID=apex
export PATH=$PATH:$ORACLE_HOME/bin
export TNS_ADMIN=$ORACLE_HOME/network/admin
export ORACLE_TERM=xterm
export ORACLE_OWNER=oracle
export TNS_ADMIN=$ORACLE_HOME/network/admin
export CLASSPATH=$ORACLE_HOME/jdbc/lib/classes12.zip
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32
export LDPATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32

So my ORACLE_HOME is /oracle/ASHOME

Now the Application server is ready for operation. Check the Application server page correctly displays using
http://hostname:port (here my port no is 7778 ie. Apache Port from Application Server 10g)

Now, Apex Installation. Download apex_3.2.zip from here
Unzip the apex_3.2.zip into a separate direcory. It will create a folder called apex. My location is /oracle/apex

4. Connect as sys user.
5. Create a tablespace for apex. i created apex32 with datafile apex32
6. Run apexins.sql

SQL>@apexins.sql apex32 apex32 temp /i/
where apex32 is the tablespace name
where apex32 is the datafile name
temp is the temporary tablespace
/i/ is the location of the image folder to be given in the configuration file. (simply give /i/)

Successful installation will have the following content at the end.

Thank you for installing Oracle Application Express. Oracle Application Express is installed in the FLOWS_030200 schema.

The structure of the link to the Application Express administration services is as follows: http://host:port/pls/apex/apex_admin (Oracle HTTP Server with mod_plsql) http://host:port/apex/apex_admin (Oracle XML DB HTTP listener with the embedded PL/SQL gateway)

The structure of the link to the Application Express development interface is as follows: http://host:port/pls/apex (Oracle HTTP Server with mod_plsql)
http://host:port/apex (Oracle XML DB HTTP listener with the embedded PL/SQL gateway)

Installation logfile will be located under /oracle/apex as installYYYY-MM-DD_HH24-MI-SS.log.

7. Change Password for ADMIN Account
- Change directory to apex
- Connect to DB as sys user and execute
- @apxchpwd

Configure HTTP Server
1. Unlock the APEX_PUBLIC_USER account
alter user APEX_PUBLIC_USER account unlock
alter user APEX_PUBLIC_USER identified by (new password)

2. Copy APEX Images
- Copy /oracle/apex/images to /oracle/ASHOME/Apache/Apache/images/ .
This is the /i/ location where we installed our images.
$cp -rf /oracle/apex/images /oracle/ASHOME/Apache/Apache/images

Adding DAD entry in dads.conf file (in /oracle/ASHOME/Apache/modplsql/conf/)

Alias /i/ “[ Put the IMAGE_LOC Value] “ as /oracle/ASHOME/Apache/Apache/images
AddType text/xml xbl
AddType text/x-component htc

<Location /pls/apex>
Order deny,allow
PlsqlDocumentPath docs
AllowOverride None
PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
PlsqlDatabaseConnectString hostname:port:SID (here my entry is genius:1521:apex (MY SID Name is apex)
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
PlsqlAuthenticationMode Basic
SetHandler pls_handler
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDefaultPage apex
PlsqlDatabasePassword APEX_PASSWORD (here my entry is welcome)
PlsqlRequestValidationFunction wwv_flow_epg_include_modules.authorize
Allow from all

</Location>

Bounce the Apache Server as
/oracle/ASHOME/opmn/bin/opmnctl stopproc ias-component=HTTP_server

or if you want to stopall, then give ./opmnctl stopall. to bounce all the services.

Now Check with
http://hostname:port:/pls/apex/apex_admin (should bring you the welcome page of the Apex with images. Here my port is 7778 as installed in Application Server 10g OHS server)
if images are not coming, then further navigation is not possible. So check with the dads.conf. Please be sure to put /" at the end of the image location. I Forget that slash, later found from the error log.



If you face any errors, look into ORACLE_IAS_ORACLE_HOME/Apache/Apache/logs/error_log.xxxxxxxxxx

Now Oracle E BIZ R12 part.
Copy the apex3.2.zip file to the server where you have to install the Application Express.
Unzip the content into a directory
Source the database environment file

1. Connect as sys user from the directory where you unzipped apex files.
2. run @apexins.sql into the database (my R12 database version is 10.2.0.3)
after completion,
unlock the APEX_PUBLIC_USER account.
Change the password using @apxchpwd.sql from apex directory.

Login to the Application server 10g server.
1. Edit the dads.conf file from /Apache/modplsql/conf/
Now add the entry

<Location pls/apex_R12>
Order deny,allow
PlsqlDocumentPath docs
AllowOverride None
PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
PlsqlDatabaseConnectString hostname:port:SID (here my entry is fserver:1521:VIS (MY SID Name is VIS in the EBIZ server)
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
PlsqlAuthenticationMode Basic
SetHandler pls_handler
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDefaultPage apex
PlsqlDatabasePassword APEX_PASSWORD (here my entry is welcome)
PlsqlRequestValidationFunction wwv_flow_epg_include_modules.authorize
Allow from all

</Location>

Now bounce the Apache of the Application server.

Test the Apex Installation by
http://hostname:port/pls/apex_r12/apex_admin

Troubleshooting is most vulnerable part here.
1. To check wwv_flow_fnd_user schema is locked or not
use
alter session set current_schema=flows_030100
/
select user_name':'account_locked':'security_group_id from wwv_flow_fnd_user
/

2. TO change the Admin Password:
Changing the Password for the ADMIN Account
In a new installation of Oracle Application Express, or if you are converting a runtime environment to a development environment, you must change the password of the internal ADMIN account. In an upgrade scenario, the password will be preserved and carried over from the prior release.
To change the password for the ADMIN account:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba

On UNIX and Linux:
$ sqlplus /nolog
connect sys as sysdba
When prompted, enter the appropriate password.
2. Run apxchpwd.sql. For example:
@apxchpwd
When prompted enter a password for the ADMIN account."

This does not require to change the password in the
ORACLE_HTTPSERVER_HOME/Apache/modplsql/conf/dads.conf File.

3. If You are getting ADMIN/ADMIN_PASSWORD as "Invalid Login Credential Error", then
run
alter user FLOWS_030200 account unlock;

connect as FLOWS_030200 and execute the procedure
begin
wwv_flow_api.set_security_group_id(p_security_group_id=>10);

wwv_flow_fnd_user_api.create_fnd_user(
p_user_name => 'admin2',
p_email_address => 'myemail@mydomain.com',
p_web_password => 'admin2') ;

end;
/

Please be sure
alter user FLOWS_030200 lock;

Then try with "admin2" and "admin2" as password. This should work...

Stuffs to Read
http://download.oracle.com/docs/cd/E10513_01/doc/index.htm

To Remove the APEX installed schema from Oracle database, Run

from apex installed directory

sql>sqlplus "/as sysdba"

sql>@apxremov.sql

Hope this will help you !!!! Cheers!!!

Demantra Issues and Troubleshooting

1. Installation of the Demantra Base Application or Patches
Create a C:/Tmp folder on the machine where the setup.exe will be executed prior to the installation as this will generate a log file to this folder

Note that there will also be some ancillary logs under the following folders:

.. Demand Planner\Database Objects\Oracle Server (Oracle back end database)
.. Demand Planner\Database Objects\Microsoft SQL Server (Sql Server back end database)

More information on troubleshooting the Demantra base installation process is found in
Note 430913.1 while additional Patch installation information is also found in Note 453127.1

2. Error starting the Web Server and/or deploying the Demantra WAR file

Review the Collaborator.log which is found under the ...Collaborator\demantra\logs folder on the webserver where Demantra is running.

Also, each individual webserver (ex. OAS, JRUN, Tomcat, Websphere, etc...) will have their own individual logs in various directories which can also be consulted.

The individual webserver documentation should be reviewed for these log locations.

3. Errors with the Demantra Batch or Simulation Engine
The key engine logs are found under the root drive of the machine where the engine is launched. The folder that holds these logs usually have Engine2k somewhere in the name.

Note that there should be at least Engine2k logs (these are the logs that show the actual splitting and forecasts that the engine does) in this folder.

However, to write the master EngineManager logs to this folder you need to go to the Engine Administrator (..Demand Planner\Analytical Engines\bin --> Settings --> Configure) and change the Engine Manager Log tab from STD to FILE.

It is NOT advised to re-register the engine after making this change

4. Stored Procedure Errors with Active_Proc_Dyn somewhere in the error message

To view the errors go to Business Modeler --> Tools --> Procedure Error Log

Note that this looks to the backend table called db_exception_log

5. End User Errors (when they occur in a Demantra worksheet) or when End User Updates Appear not to be Processed/Saved Correctly.

The important log that we want to get usually with end user issues (ex. screen freezes, error messages appear when running or editing a worksheet, end user updates are not being processed*, etc..) is the Java Plugin Log.

There are two ways to get this log:

1) In the bottom, right hand part of the machine you will see a Java coffee cup icon. Right click on it > Open Console. Note that if there are more than one icon then look for the log that references Demantra in the URL

To make sure you are not including old messages, press the Clear button and then try to recreate the issue again.

2) If the machine has frozen up then a log is still usually saved on the back end of the machine. This can usually be found by going to C:/Documents and Settings//Application Data/Sun/Java/Deployment/log

If there are no errors evident in the java plugin log then go to the Collaborator.log found under:

http://<>/demantra/admin/systemLogs.jsp
So for example if you normally log into Demantra using the following URL:

http://DEMANTRAMACHINE:8080/demantra/portal/loginpage.jsp

then these logs would be accessed by going to:

http://DEMANTRAMACHINE:8080/demantra/admin/systemLogs.jsp
An alternative way to view these logs is to go directly the machine hosting the webserver and go to the logs found under ...Collaborator\demantra\logs

Look for the entries in the log around the time of the error (note that the webserver might be in a different timezone so an error for an enduser in New York at 4pm will show up at 1pm in the Webserver based in California)

Enhanced Logging for End User issues can be recorded by going to:
http://<>/demantra/admin/loggerManager.jsp
Once there, turn on the following lines:

appserver.sql
appserver.audit_trail_sql
appserver.update.operation
appserver.update.processapp
server.update.sqlappserver.retrieve.sqlapp
server.retrieve.data.sql

Note that this logging will be turned off either by the next time the webserver is restarted or by the user turning off the lines that were earlier turned on.

*For issues where updates are not being reflected in the series after re-running the worksheet, and there doesn't appear to be any errors in the Java Plugin or Collaborator.logs, then close out of the worksheet completely and try to re-run the worksheet one more time.

If the update is then reflected that that usually points to a possible issue the last_update_date column and needs to be addressed differently. It should also be mentioned to Oracle Support if this problem with updates only recently started occurring with this series or if this is a new series that is being tested out.

6. Workflow Errors
Although the root cause might lie in another log, the first log that should be checked is the Collaborator.log This log can be accessed by going to the following URL:

http://<>/demantra/admin/systemLogs.jsp

So for example if you normally log into Demantra using the following URL:

http://DEMANTRAMACHINE:8080/demantra/portal/loginpage.jsp

then these logs would be accessed by going to:

http://DEMANTRAMACHINE:8080/demantra/admin/systemLogs.jsp
An alternative way to view these logs is to go directly the machine hosting the webserver and go to the logs found under ...Collaborator\demantra\logs

Look for the entries in the log around the time of the error (note that the webserver might be in a different timezone so an error for an enduser in New York at 4pm will show up at 1pm in the Webserver based in California).

Enhanced Logging for Workflow issues can be recorded by going to:

http://<>/demantra/admin/loggerManager.jsp
Once there, turn on any line that has Workflow in it and then re-run the workflow in question. Note that this logging will be turned off either by the next time the webserver is restarted or by the user turning off the lines that were earlier turned on.

If the error is in a Transfer step then you might need to consult that Integration Interface logs in the next section of this document.

7. Integration Interface / Transfer Step / APS.bat / APS.exe Errors
Although the root cause might lie in another log, the first log that should be checked is the Integration.log This log can be accessed by going to the following URL:

http://<>/demantra/admin/systemLogs.jsp

So for example if you normally log into Demantra using the following URL:

http://DEMANTRAMACHINE:8080/demantra/portal/loginpage.jsp

then these logs would be accessed by going to:

http://DEMANTRAMACHINE:8080/demantra/admin/systemLogs.jsp

An alternative way to view these logs is to go directly the machine hosting the webserver and go to the logs found under ...Collaborator\demantra\logs

Look for the entries in the log around the time of the error. Note that errors might also be found in the following tables:

- _ERR (ex. if the staging table is name MSD_DEM_PRICE_LIST then the error table would be MSD_DEM_PRICE_LIST_ERR)

The above ERR table is when it is going from the staging table (ex. MSD_DEM_PRICE_LIST) to the main integration staging tables,

UPDATE_BATCH_TRAIL and UPDATE_BATCH_VALUES.
UPDATE_BATCH_TRAIL_ERR and UPDATE_BATCH_VALUES_ERR

The above ERR table is when it is going from the integration staging tables UPDATE_BATCH_TRAIL and UPDATE_BATCH_VALUES to the final Demantra table (ex. Sales_Data)

Each of the above ERR table will have a message field with at least a brief description of why it was kicked out.

8. Errors with Member Management or Chaining
Note that issues with actually launching these two applications from the Collaborator Workbench and other silent installer issues should be addressed by reviewing Note 463049.1

Errors that occur in Member Management might be seen by going to

Business Modeler --> Tools --> Procedure Error Log

Note that this looks to the backend table called db_exception_log

Errors that occur during Chaining* might also be might be seen by going to

Business Modeler --> Tools --> Procedure Error Log

An additional error message table for Chaining is the Chains_Queue table (can only be viewed by use of SQL commands).

*It should be noted that this error has to do with when the Status states 'Failed' and is not meant to cover legitimate warning messages like 'No Common Population or Source' indicating that the setup of your chaining profile is possibly incorrect.

9. Issues with EBS Integration to Demantra

In general, most EBS side activities (ex. Planning Data Pull) can be logged using Note 245974.1 however, the Shipment and Bookings Collection job can have extra logging turned on by changing MSD_DEM: Debug Mode to Yes (default is No).

Note that as the Shipment and Bookings Collection job moves to the other side of the wall from EBS side of the database to the Demantra side of the database (usually indicated by when you start seeing references to the Demantra schema or tables like t_src_items_tmpl or t_src_sales_tmpl_err) then the errors may need to be tracked using the Workflow or Active_Proc_Dyn troubleshooting sections of this note.

10. Error with Legacy Demantra Scheduler Application (ex. Manuals_Ins)

Prior to Demantra Version 6.x, when the application became a Web Based front end application, clients would have used a native Demantra application commonly referred to as Scheduler. This scheduler would run various stored procedures at set intervals. The most important of these jobs was the Manuals_Ins stored procedure which pre-dates the asynchronous Java Updater (the latter which came into the application starting in v7.x). To track the errors from any of the procedures/jobs in the Demantra Scheduler then go to the logs found under the ..Demand Planner\Scheduler\bin folder.

So in summary, most clients who have the Scheduler running at their site are going to be pre-Version 6.x clients but you might have some clients on Version 6.x and early Versions of 7.0.x that have it running in place of the newer Workflow Manager application.