Oracle E-Business Suite: Forms Compilation Error - Form Derleme Hatası

In R12.1.3

Recently we have encountered errors such as these:


Compiling KEY-NXTBLK trigger on QUERY_FIND data block...
Compilation error on KEY-NXTBLK trigger on QUERY_FIND data block:
PL/SQL ERROR 49 at line 1, column 1
bad bind variable 'parameter.G_query_find'
PL/SQL ERROR 49 at line 1, column 1
bad bind variable 'parameter.G_query_find'
PL/SQL ERROR 49 at line 3, column 1
bad bind variable 'parameter.G_query_find'

It turned out that FORMS60_PATH was not set correctly. Whenever forms are compiled FORMS60_PATH is set to:

FORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resource

In context file it was set as:

$AU_TOP/resource:$AU_TOP/resource/stub

After correcting this and compiling manually it worked. To make this permanent change the s_f60path to include $AU_TOP/forms/US:$AU_TOP/resource

In R12.2.4 or in R12.2 we should be adding the following to the $FORMS_PATH variable in the context file which is in the $APPL_TOP/$SID_$HOSTNAME.env path  

$AU_TOP/forms/US:$AU_TOP/forms/TR 

After that forms can be compiled with the following command.

E.g.:

frmcmp_batch AKDFLOWB.fmb   apps/apps output_file=$AK_TOP/forms/TR/AKDFLOWB.fmx compile_all=special;


Referanslar:

Forms Compilation hatası
http://oracleappstechnology.blogspot.com.tr/2009/03/forms-compilation-errors.html

Oracle Fusion Middleware: Running RDA For Hyperion - Remote Diagnostic Agent(RDA) - Hyperion için RDA Çalıştırmak

We have written about the RDA before for OBIEE and EBS.

1- http://berkeoz1.blogspot.com.tr/2014/01/oracle-e-business-suite-rda-nedir.html
2- http://berkeoz1.blogspot.com.tr/2014/07/oracle-fusion-middleware-running-rda.html

Now we would like to specify the usage of rda for Hyperion. The need to that has arisen to detect problems in the Hyperion system. What we had used before was the diagnostic tool of Hyperion.
(http://berkeoz1.blogspot.com.tr/2014/08/oracle-hyperion-starting-and-stopping.html)
However we will be using rda as a complementary tool to our diagnostic efforts.

Where is RDA?

RDA is found in the Middleware Home. (For example:E:\Oracle\Middleware\oracle_common\rda)

We could do the setup which is giving the appropriate details for running rda by "rda.cmd -S".

To list all the profiles that we can run we could use:

rda.exe -L

With that command all the modules and previously defined profiles to analyze the system can be found.



An example of the command to run RDA with using just the HFM module is below:

rda.cmd -vSCRP HFM

An example of the command to run RDA with using profile for HFM is below:

rda.cmd -vSCRP -p Hyperion1112_HFM

In the end, we would have something like the directory structure below in which we run first the "RDA_index.htm" file

References:

1-How to Use Remote Diagnostic Agent (RDA) to Gather Diagnostic Information On Oracle Hyperion Financial Management (HFM) Servers to Help Resolve Service Requests Faster [Video] (Doc ID 1100612.1)

Oracle Fusion Middleware: Error Assigning Users To Application Role in OBIEE 11g - Kullanıcuların Uygulama Rolüne Atanırken Hata Alması

After installing OBIEE 11.1.1.7 on our system, we encountered with an error. This error was occuring although we had succesfully set our Active Directory. Our AD setup was working fine and we were logging in to system with the AD accounts.

Regarding the setup, you could check on how we have done it.
1-rovider - Active Directory Authentication to OBIEE 11g - Active Directory Configuration'ını OBIEE 11g İçin Yapmak

2-hentication to OBIEE 11g - 2 - Deleting Default Provider - Active Directory Configuration'ını OBIEE 11g İçin Yapm

The error that we have seen is

Java.lang.NullPointerException
#{viewScope.emas_pagemodel_security_EditAppRole.searchPrincipal}: java.lang.NullPointerException
     Hide Additional Trace Information

The error screen was like the picture below:

After that we have searched for the error, we have seen that there was a bug concerning this problem.

"Bug 16808088 : 11G JAVA.LANG.NULLPOINTEREXCEPTION ADDING USER TO ROLE AFTER UPGRADE TO 11.1.1.7"

The proposed solution is to set the virtualize parameter to false if it ise set. Virtualize parameter doesn't work with the username.attr which we have previously set in the security provider configuration settings.

In the end, we changed its value to false and we were able overcome this problem.

Reference:
1- https://community.oracle.com/thread/2530201?start=0&tstart=0

Oracle Fusion Middleware: EVALUATE_SUPPORT_LEVEL Error in Oracle OBIEE 11g

EVALUATE_SUPPORT_LEVEL errror appers when we open a report from a catalog or a dashboard. It has a quite simple solution.







In order to to solve this problem, we change evaluate support level parameter in the NQSConfig.ini file to the value given below:

EVALUATE_SUPPORT_LEVEL=2


After that, we could restart the BI server to activate the changes.

Oracle Fusion Middleware: Using Active Directory as a User Provider - Active Directory Authentication to OBIEE 11g - 2 - Deleting Default Provider - Active Directory Configuration'ını OBIEE 11g İçin Yapmak ve Default Provider'ı Kaldırmak

In our previous article, we explained how to add Active Directory as an user provider. Now we will delete the default authenticator in order to make the newly added Active Directory our only provider to have a tighter security configuration.

2.Deleting Default Provider

The reason why we put 2 at the beginning is that we are assuming that we have added the Active Directory just like we did on the arcticle before this.

2.1 Update the Credential Store Password

These configuration changes can be made from entreprise manager. The link should be like this: http://localhost:7001/em

Open Weblogic Domain / bifoundation_domain screen. Select Security / Credentials item under WebLogic Domain menu.

Find “system.user” under oracle.bi.system and click Edit.

Input the new user name and password. We have created OBIA_BISystemUser just for this purpose. We will use it later to add more privileges to our system user.

2.3. Security Provider Configuration

Click “WebLogic Domain” menu. Click “Security Provider Configuration” menu item under Security sub-menu.

We then add the following properties.

Property Name	Value
virtualize	false
user.login.attr	samaccountname
username.attr	samaccountname

2.4. Assign application roles to system users and groups

Select Business Intelligence / coreapplication from left panel. Click on Security / Application Roles item on Business Intelligence Instance menu.

Make the following assignments :

Role Name	Members
BISystem	OBIA_BISystemUser (User)
BIAdministrator	OBIA_Administrators (Group)
BIAuthor	OBIA_Administrators (Group)
BIConsumer	OBIA_Administrators (Group)

Note: The users and the groups are newly created. The creation process is explained on the first part of this arcticle.

2.5. Assign global roles to system users and groups:

Open Weblogic Admin Console. Go to “myrealm” in WebLogic Admin Console. Go to Roles and Policies tab. In “Realm Roles” sub tab, expand Global Roles / Roles.

Assign the roles to LDAP groups as seen in the following table.

Global Roles :	Assignment :
Admin	Group : OBIA_Administrators User : OBIA_BISystemUser
AdminChannelUsers	Group : OBIA_Administrators
AppTester	Group : OBIA_Administrators
CrossDomainConnector	Group : OBIA_Administrators
Deployer	Group : OBIA_Administrators
Monitor	Group : OBIA_Administrators
Operator	Group : OBIA_Administrators

2.6. Delete default provider:

Go to Providers tab under security realm “myrealm”. Click on Active Directory provider we created. Select REQUIRED in Control Flag dropdown field. Click Save.

2.7. Stop and start BI services:

Click “Stop BI Services” under “Oracle Business Intelligence” group in Start Menu. To proceed, we have to provide weblogic user and its password in the console.

Delete the two boot.properties files in the following locations :

%OBI_HOME%\user_projects\domains\bifoundation_domain\servers\AdminServer\security

%OBI_HOME%\user_projects\domains\bifoundation_domain\servers\bi_server1\security

Click “Start BI Services” under “Oracle Business Intelligence” group in Start Menu.

Enter the user and password of OBIA_Weblogic when prompted.

Oracle Fusion Middleware: Using Active Directory as a User Provider - Active Directory Authentication to OBIEE 11g - Active Directory Configuration'ını OBIEE 11g İçin Yapmak

In Oracle OBIEE 11g, we could use AD(Active Directory) as an LDAP source. Therefore we could use the users and their accounts which are defined in AD server. To do that, we have some configuration tasks to apply in Oracle Weblogic Server and Fusion Middleware Control which is  also known as Oracle .

1. Creating a New Provider

1.1. Create System Users & Groups in Active Director:First step is to create some of system users in AD. These are:

OBIA_Weblogic, OBIAOracleSystemUser, OBIA_BISystemUser

We also need to create 2 groups in AD. These are

OBIA_Administrators(Member:OBIA_Weblogic) and OBIAOracleSystemGroup(OBIAOracleSysUser)

The reason why we added prefixes like OBIA is to make them specific to our installation.

1.2 Backup of Configuration: 

The given config.xml file is where we %OBI_HOME%\user_projects\domains\bifoundation_domain\config\config.xml

In case we  make an error, we should have a backup of this file. If we ever have a problem with the opening of Oracle Weblogic, we could solve this problem by returning to the old configuration file.

1.3 Creation of Active Directory Provider:

Lets login to the Weblogic Admin Console: http://localhost:7001/console. Ports and links  may change according the installation you are making.

Click Security Realms on left panel. Click “myrealm” on Realms list. Go to Providers tab. Click Lock & Edit button on left panel. Click NEW. 

Specify the name for new authentication provider as you like.  Select “ActiveDirectoryAuthenticatior” from the TYPE drop-down list. Click OK. Click on the newly created Active Directory provider.

Select SUFFICIENT from Control Flag drop down list. Click SAVE. Then we fill the Provider specific properties. 

Connection / Host	Active Directory IP
Connection / Port	389
Connection / Principal	cn=obia_weblogic,cn=users,dc=gm,dc=,dc=com,dc=tr
Connection / Credential	Passw0rd
Connection / SSLEnabled	NOT SELECTED
Users / User Base DN	dc=gm,dc=,dc=com,dc=tr
Users / All Users Filter
Users / User From Name Filter	(&(samaccountname=%u)(objectclass=user))
Users / User Search Scope	subtree
Users / User Name Attribute	samaccountname
Users / User Object Class	user
Users / Use Retrieved User Name as Principal	SELECTED
Groups / Group Base DN	cn=users,dc=gm,dc=,dc=com,dc=tr
Groups / All Groups Filter
Groups / Group From Name Filter	(&(cn=%g)(objectclass=group))
Groups / Group Search Scope	subtree
Groups / Group Membership Searching	limited
Groups / Max Group Membership Search Level	1
Groups / Ignore Duplicate Membership	NOT SELECTED
Groups / Use Token Groups For Group Membership Lookup	NOT SELECTED
Static Groups / Static Group Name Attribute	cn
Static Groups / Static Group Object Class	group
Static Groups / Static Member DN Attribute	member
Static Groups / Static Group DNs from Member DN Filter	(&(member=%M)(objectclass=group))
Dynamic Groups / Dynamic Group Name Attribute
Dynamic Groups / Dynamic Group Object Class:
Dynamic Groups / Dynamic Member URL Attribute
Dynamic Groups / User Dynamic Group DN Attribute
General / Connection Pool Size	0
General / Connect Timeout	20
General / Connection Retry Limit	3
General / Parallel Connect Delay	0
General / Results Time Limit	0
General / Keep Alive Enabled	NOT SELECTED
General / Follow Referrals	SELECTED
General / Bind Anonymously On Referrals	NOT SELECTED
General / Propagate Cause For Login Exception	NOT SELECTED
General / Cache Enabled	SELECTED
General / Cache Size	32
General / Cache TTL	60
General / GUID Attribute	samaccountname

Click DefaultAuthenticator from the Provider list.

Select SUFFICIENT from Control Flag drop down list. Click SAVE.

Click Activate Changes button from Left Panel. Stop and start BI Services for these changes to take effect. 

1.4 Check If Integration Works

Login Weblogic admin console and go to Provider list. Click on Users and Groups tab.

See if users and groups from Active Directory are listed. 

1.5 Security Provider Configuration

Click “WebLogic Domain” menu in Enterprise Manager. Click “Security Provider Configuration” menu item under Security sub-menu.

Add the following property to the custom properties.

Property Name	Value
virtualize	true

Now we shoud be able to login to the environment with both our default authenticator and with the users from active directory users.

References:

1-http://www.peakindicators.com/media_pi/Knowledge/oracle%20bi%2011g%20-%20active%20directory%20authentication.pdf

2- TechNote: Configuring Oracle BI 11g and Weblogic for Single Sign-On using Kerberos-based Windows Authentication backed by Active Directory.
An Oracle White Paper
Updated October 2011

Oracle Hyperion: Starting and Stopping HFM 11.1.2.3

START:

EPM System Installer provides us a single start script under EPM_ORACLE_INSTANCE/bin which is called start.bat depending on the operating system.
To start the system, we start from foundation server, and run the start.bat under the "E:\Oracle\Middleware\user_projects\epmsystem1\bin". Then we pass on to the application server and run the start.bat which also under this or a similar path "E:\Oracle\Middleware\user_projects\epmsystem2\bin".

To check if we have succeeded on starting the application, we could run EPM System Diagnostics.

STOP:

Stoping procedure is quite similar to starting procedure. To stop we could start from the application server then stop the foundation server.


What is  EPM System Diagnostics?

Epm System Diagnostics is a tool that makes the essantial checks on a system and produces a report in which it shows its analysis. EPM System Diagnostics can be found on both of the servers(Applciation and Foundation). After the analysis, reports are created int the following path which may change according to the installation "E:\Oracle\Middleware\user_projects\epmsystem2\diagnostics\reports\"
Example:"E:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\instance_report_20140813_034231.html"

These reports can be used to for historical evalution. For example to estimate a time period where  we have last succeeded on running some module or when some module just crashed, we could always check these things.

System Diagnostics exe can be found in the  EPM_ORACLE_INSTANCE/bin

EXE's  and URL's 

Oracle Hyperion Shared Services Console: http://machine_name:Port/interop.  This is found on the Foundation Server. Example: http://machine_name:28080/interop

EPM Workspace: Http://machine:port/workspace. Workspace URL's can be also found on foundation services.
Example. http://machine_name:19000workspace