Stream Exception: javax.xml.stream.XMLStreamException: Premature end of file encountered -- Weblogic Forced Shutting down

Weblogic Forced Shut down some times.......

Some time, suddenly weblogic will go down while doing deploy to application server in hyperion configuration. Error msg seems like below,

                                   

Go and Check in the following location, 

C:\Oracle\Middleware\user_projects\domains\EPMSystem\config\fmwconfig

Check system-jazn-data.xml file has data or not, as shown below screen (it is 0KB here)

In the below, you can find backup file of the same file. So rename one file as system-jazn-data.xml and start weblogic again

Now check, Weblogic will be in Running mode after some time

Thanks,

Mady

Financial Close Management installation and Configuration in 11.1.2.3 - SOA to existing domain

Financial Close Management installation - SOA to existing domain

first of all, why i am talking about SOA while talking Financial close Management, because we must install SOA to install Financial Close Management.

Second one, 

Already if we have existing hyperion environment with weblogic server, so we can deploy SOA to existing domain. While installing SOA, but it will create separate managed server for like soa_server1(default). We need to start Managed server separately. It won't start with normal start of Weblogic admin server.

Deploy SOA to existing domain:

Situation: 

1. Installed and Configured Hyperion suite(Essbase, Planning, HFM, FDM, FR etc)

2. we have existing weblogic domain (EPMSystem)

3. Installed SOA on the top of EPM Suite.

Configuration SOA:

Go to Start --> All Programs --> (SOA folder) --> Configure Application Server

Select second option, Extend an existing Weblogic domain

Select existing Weblogic domain EPMSystem( which is used for EPM suite)

Select Oracle SOA suite, Oracle WSM Policy Manager and Click Next

Click Next with default settings

Wizard will checks JDBC connections, Click Next

Set Password for SOA Infrastructure, User Messaging Service, OWSM MDS Schema, SOA MDS Schema by selecting and click Next

Wizard will check JDBC connections, click Next if test Successful

click Next with default settings

click Extend to start deployment

Domain Extension applied successfully.

Next tasks:

Once deployement done, Start soa_server1 Managed server using the below command:

Note: 

1. Make sure you installed HFM, FDM, FR to support for FCM.

2. Make sure Weblogic domain started.

3. Make sure soa_server1 managed server started.

Create Weblogic User:

1. Log into Weblogic console

http://<servername>:7001/console

2. click on Lock and Edit

3. Click on Security realm

4. click on myrealm

5. select tab Users and Gropus

6. Create user with name of Shared Services.

Click on New to create new user. Password must contain numeric, letters. special char(optional).

NOTE: FCM does not support using HSS Native Directory Users. However for testing, training or demo environments ONLY, native users can be added to both the HSS Native directory and the Weblogic native directory.

In a Production environment, only MSAD or other LDAP External Directories are supported for FCM.

Now login to workpsace and try to access Financial close from Navigate --> Applications.

While accessing if it asks for login. Enter username and password which we created in weblogic.

Enjoy FCM.

Thanks,

Mady

How to patch the environment in Hyperion?? -- 500 patch applying

What is Patch and Why we need to apply Patch??

Patch: To add new features to the existing environments with modifying simple codes in the background, Vendor will release patches instead of next version.

Why Patch: After releasing version, may vendors got response from users or clients like they are facing issue in using some features. Those might be bugs in that version. So, Development Team will work on those bugs and Vendor will release Patch to add the functionality to the existing version.

Now, Main part in patching.....!!!! How to apply Patch??

Go to Oracle My Support and search for Patches.

Click on Read Me, to get patch instructions.

Here also, i am briefing how to apply

Download and unzip to the following path, (Change Drive name as per your environment)

C:\Oracle\Middleware\EPMSystem11R1\OPatch

As Mentioned in Read Me, first see Prerequisites before applying patch.

for example, we have FDM in our environment, for this we need to change Enable 32bit application to false in IIS.

Go to Command Prompt and change path to OPatch Location and execute the Opatch as mentioned in Read Me.

and we get result as OPatch Succeeded.

Now my 11.1.2.3 environment patched with 500 patch.

Thanks,

Mady

Error [102000000] detected in member : Level 0 virtual members must have a formula associated with them + HSP_UDF

Error [102000000] detected in member : Level 0 virtual members must have a formula associated with them

Solution:

1. Remove UDA from planning application.

2. Administration >> Dimensions >> Select Dimension at issue >> Search for Member at issue >> Select Member at issue> > Select Edit >> Select UDA tab and remove the HSP_UDF from the saved selection.

3. Enable the UDA of HSP_UDF directly via the Essbase outline.

4. This can be done via Essbase Administration Services >> Applications >> Outline > Select right-click on Outline and select option to Edit > Search for member at issue in the outline > Right-click on the Member and select Member Properties > UDA's > Enter HSP_UDF in the Assign field and hit OK.

5. Refresh Database from Planning

Thanks,

Mady

Unable to obtain lock for Registry database in Hyperion Configuration

Unable to obtain lock for Registry database in Hyperion Configuration 

1. whenever we start Configuration in Hyperion, EPM Configurator will create one lock in the Relational Database. Once we close EPM Configurator, this lock table entry will be create automatically. But in case of table entry not deleted, EPM Configurator will throw error as below.

In Shared services schema or Database, the table and lock record,

Table name: EPM_REGISTRY_LOCK

Delete the table entry or lock record then run EPM Configurator. Click Next it will allow you to the Next page.

Entered into the Next page, Continue with Configuration...

                                                         Thanks,

                                                           Mady

javax.naming.CommunicationException Root exception is java.net.ConnectException t3://servername:port: Destination unreachable

Issues in hyperion 11:

Error msg:

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://<servername>:<port>: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
atweblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306) at weblogic.jndi.Environment.getContext(Environment.java:166)
at weblogic.jndi.Environment.getInitialContext(Environment.java:145)
atweblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(MBeanHomeTool.java:172)
at weblogic.Deployer.runBody(Deployer.java:709)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.Deployer.runMain(Deployer.java:566)
at weblogic.Deployer.main(Deployer.java:549)
Caused by: java.net.ConnectException: t3://ep-prdapp1:10080: Destination unreachable; nested exception is java.net.ConnectException: Connection refused; No available router to destination 

at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
... 8 more 

Solution:

This is an issue with the replication of the Embedded LDAP updates and is defined by the replicas.prop property file.

Find user_domain \ user_server \ ldap \ conf \ replicas.prop, edit this file, deleted all the content and add the following text: 

Replica.num = 0

Re-start the server.

Note: You can back up the replicas.prop file before editing it. The file may be empty or have some text.

JPS-01050: Opening of wallet based credential store failed.

JPS-01050: Opening of wallet based credential store failed. 

Reason java.io.IOException: PKI-02002: Unable to open the wallet.

Check password.

Server state changed to FORCE_SHUTTING_DOWN (Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.)

 When starting Weblogic, we are getting the issue in weblogic and it going down automatically.

 <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.

weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.

Solution:

We navigated to <Middleware_Home>/user_projects/domains/<Your Domain>/config/fmwconfig/ folder and observed that cwallet.sso is corrupted and file size is 0(zero) kb . Here we renamed this file(cwallet.sso_bkp) and successfully started Adminserver .