DAC 11g code migration information tabs

 In this post, we will discuss about the created patch and applied patch information.

 When you create a DAC metadata patch or apply a patch, this information will be stored in DAC setup tab for future references.

Created patch:

 Created patches will be stored in DAC -> Setup -> "Working Patches" tab.

 In this tab, you will get the information about, when the patch created,what are the contents in it, its status and last exported time.

Applied patch:

 Applied patches will be store in DAC -> Setup -> "Applied Patches" tab.

 In this tab, you will get all the applied patches information, what patches were applied and its status.

DAC metadata patch failing with errors

  I was working on creating DAC metadata patch to migrate subset of code to another environment. Previously i could migrate it successfully. But due to some mistake that I have done while creating patch produces below error message while applying the patch in another environment.

 So I created a patch again correctly and could resolve this issue.

1) , of table W_ETL_SA_STEP is not added or updated to repositoryMESSAGE:::Subject Area Task - Link must have [Task]
EXCEPTION CLASS::: com.siebel.analytics.etl.api.exception.RequiredPropertyMissingException

com.siebel.analytics.etl.api.object.SAStepObject.checkForRequiredProps(SAStepObject.java:157)
com.siebel.analytics.etl.api.object.BaseAPIObject.persist(BaseAPIObject.java:375)
com.siebel.analytics.etl.api.object.BaseAPIObject.persist(BaseAPIObject.java:296)
com.siebel.analytics.etl.inc.objects.IncXMLReader$PersistInfo.persist(IncXMLReader.java:1941)
com.siebel.analytics.etl.inc.objects.IncXMLReader$CurrTableInfo.persistCurrentObjects(IncXMLReader.java:2166)
com.siebel.analytics.etl.inc.objects.IncXMLReader$CurrTableInfo.addObject(IncXMLReader


2) , of table W_ETL_SA_STEP is not added or updated to repositoryMESSAGE:::persists error: null STEP_WID is not specified!
Can't update a record!
EXCEPTION CLASS::: com.siebel.analytics.etl.api.exception.BaseAPIException

com.siebel.analytics.etl.api.object.BaseAPIObject.persist(BaseAPIObject.java:405)
com.siebel.analytics.etl.api.object.BaseAPIObject.persist(BaseAPIObject.java:296)
com.siebel.analytics.etl.inc.objects.IncXMLReader$PersistInfo.persist(IncXMLReader.java:1941)
com.siebel.analytics.etl.inc.objects.IncXMLReader$CurrTableInfo.persistCurrentObjects(IncXMLReader.java:2166)
com.siebel.analytics.etl.inc.objects.IncXMLReader$CurrTableInfo.addObject(IncXMLReader.java:2126)
com.siebel.analytics.etl.inc.objects.IncXMLReader.createAPIObjectNew

3)

createAPIObject fails with error: null, container id =,Oracle 11.5.10EXCEPTION CLASS::: com.siebel.etl.gui.core.NewRecordCreationException

com.siebel.analytics.etl.client.data.model.ResultSetParser.createNewRecord(ResultSetParser.java:203)
com.siebel.analytics.etl.client.data.model.UpdatableDataTableModel.createNewRecord(UpdatableDataTableModel.java:98)
com.siebel.analytics.etl.client.data.model.DACTableModel.createNewRecord(DACTableModel.java:326)
com.siebel.analytics.etl.api.object.BaseAPIObject.persist(BaseAPIObject.java:361)
com.siebel.analytics.etl.api.object.BaseAPIObject.persist(BaseAPIObject.java:296)
com.siebel.analytics.etl.inc.objects.IncXMLReader$PersistInfo.persist(IncXMLReader.java:1941)
com.siebel.analytics.etl.inc.objects.IncXMLReader

Export Multiple Informatica workflows from different folders as single xml file

 Export Multiple Informatica workflows from different folders as single xml file

 I am sharing a technique where you can export multiple Informatica workflows from different folders. Usually you can export workflows from one folder at a time. But sometimes you need to export it as one xml file and this is not possible with regular approach. 

So for those people who got this requirement just follow this steps.

 I have already explained Usage of Informatica Query option, so by making use of this option we will complete this export activity.

Step 1: Create a query such that i will list out all the required workflows from different folders.

Step 2: Execute the query to create the output. You will see the output with workflows from different folders as marked in red color in the below image.

Step 3:  Use ctrl(key) to select all the workflow and do right click on it and select "Export to XML file" option.

Step 4: Now you can save all the workflows as single xml file from different workflows.

Related links:

Listing Informatica objects with Query Tool

./nqcmd: error while loading shared libraries: libARicu23.so:

 In this post I am going to explain how to use "nqcmd" command line utility in Linux environment.

Please follow the same steps as mentioned. Otherwise the while invoking nqcmd utility you will face some library file error issue.

./nqcmd: error while loading shared libraries: libARicu23.so: cannot open shared object file: No such file or directory

 As oracle says, to use nqcmd utility, we have to run "bi-init.sh" which initializes Oracle Instance. This file will be available in the below path.

 /OBIEE/app/fmw/instances/instance/bifoundation/OracleBIApplication/coreapplication/setup/

Step 1: Open putty and connect to the linux server and then change directory to the below path.(Path may be different according your environment)

cd /OBIEE/app/fmw/instances/instance/bifoundation/OracleBIApplication/coreapplication/setup/

Step 2: Run bi-init.sh file exactly as below.

. ./bi-init.sh

Note: First dot space and second dot and immediate backslash.

Step 3: Now change directory to the below path

cd /OBIEE/app/fmw/Oracle_BI1/bifoundation/server/bin

Step 4: Execute the nqcmd with below command and without any error it will invoke.

[obiee@obieedevlinux bin]$ ./nqcmd

 Here the Important step is Step 2: to set Oracle Instance.

Download OBIEE 11g server logs from Enterprise manager

 When we face some trouble in OBIEE 11g, we always search for the log files to find out the cause. 

Examples of log files are 

 1) Presentation Services log (sawlog.log)
 2) Server log (nqserver.log & nqquery.log)
 3) Schedule log (nqscheduler.log)
 4) JavaHost log (jh.log)
 5) Cluster Controller log (nqcluster.log)

 6) OPMN log (opmn.log)

 To get/view this files either you have to connect to the server using ssh(putty) or filezilla(ftp). Sometime you will not have server login passwords. So in this case getting these files are very difficult. 

 Here is the tip to download the above log files directly from OBIEE 11g Enterprise manager.

Step 1: Login to EM.

Step 2: Right click on the "bifoundation_domain", then "Logs" and select "View Log Messages".

Step 3: You will see the log files screen as below.

Step 4: Expand "Selected Targets" as shown below and you will see the log files here.

Step 5: Then select desired server log and click on the "view log file" ( Marked with red color in the screenshot).

Step 6: Here you can either view the required log or you can directly download the entire log file in to your local machine.

 Similarly you can follow the same steps for downloading other log files also.