Friday, 31 March 2017

Error RCU-6080 while installing RCU for OBIEE 12c

Error: RCU prerequisite check failed with error code RCU- 6080 while configuring RCU for OBIEE 12c.



Cause: The reason for the failure is, from OBIEE 12c onwards oracle prefer to install the obiee metadata schema in pluggable database rather than container database. While installing database 12c we will get a prompt to select install pluggable database with the current installation. So by default in 12c we have a pluggable database with object name 'PBDORCL'. So instead of using ORCL  use PDBORCL as service name and try to create the schema.

But before using pluggable database please make sure that the DB is in open state. Because when starting DB oracle only open the default DB ORCL, So it will be better to use a trigger to open the pluggable DB PDBORCL.

Command to check the MODE of database.

"SELECT NAME ,OPEN_MODE FROM V$PDBS"


Then you can see the OPEN_MODE as mounted so please below command to open the portable database.

ALTER PLUGGABLE DATABASE ALL OPEN;
After executing the command the database will open and that will be available for read and write.

you can use the below trigger for opening pluggable database.

CREATE OR REPLACE TRIGGER OPENPBD AFTER STARTUP ON DATABASE
BEGIN

     EXECUTE IMMEDIATE 'ALTER PLUGGABLE DATABASE ALL OPEN';
END OPENPBD;


Then replace the service name with pdborcl and run the RCU prerequisite one more time.

now you can see the step passed and you can continue with the installation.


Thank you .



INST-07545: Unexpected error while installing OBIEE 12c Client.

Error:INST-07545: Unexpected error the distribution setup_bi_client 12.2.1.2.0 incompatible features with the following.....



Cause: This issue is because we are trying to install the obiee12c client in the same oracle_home where we installed our obiee12c.


Action: Change the oracle installation directory to a fresh directory and continue with the installation.

As shown below i changed the directory into C:\OBIEE_ClientHome

Then the issue is resolved and able to proceed with the installation.


Thank you :).





Wednesday, 30 November 2016

Connecting to ORACLE database from SSIS

Issue: I have to connect to ORACLE database from my SSIS tool.

Solution: Download and install

32-bit Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studio 

Using the following link:http://www.oracle.com/technetwork/topics/dotnet/utilsoft-086879.html

Then install the driver and it ask for data base details before the final step.So provide the DB Name(Just a name),Host name,Port,Service name

After competing installation restart your machine.

Then open your SSIS and select OLEDB Source and create a new connection.

From the Provider select Oracle Provider for OLEDB.



Then it will ask for the server or file name, give the name of your DB that you provided during installing the client.(Entry in your tnsnames.ora) Then give username and password and test the connection.


You can see connection successful and you can connect to the database and select the tables. 

Friday, 18 November 2016

Issue while Converting String to Int data type in SSIS Source Excel.

Issue: When converting String data type to Int using data conversion in SSIS, The transformation failing with conversion error.Source used is Excel

Cause: Excel source file contain Nulls and empty values. So because of empty string we are not able convert the values.

Solution:Add a derived column transformation and add the following expression for the derived column.

Expression: ISNULL([COLUMN_NAME]) || TRIM([COLUMN_NAME]) == "" ? (DT_I4)0 : (DT_I4)[COLUMN_NAME]

Then use this derived column in the output.

So if there is empty string or null values that will be replaced with O else with the column name.

Thank you.

Monday, 24 October 2016

SSIS Error "DT_GUID" cannot be used with binary operator "!=" while doing incremental load.

Issue:

While doing incremental load in SSIS we have a condition to chehck whether source and target column values are same or not

So in Conditional Split transformation we did a comparison like
[Source_colum != Target_Column]

But when we used a column with data type uniqueidentifier we encountered an issue as shown below.


Cause: 

The column that we used for comparison have data type DT_GUID and that cannot be used for binary operation.

Solution:

Cast the datatype to character and we can use that for comparison.

SSIS format for casting to string  (DT_STR,50,1252)[Colum_Name]

(DT_STR,30,1252) casts 30 bytes, or 30 single characters, to the DT_STR data type using the 1252 code page.


So code used for comparison (DT_STR,30,1252)Source_column != (DT_STR,30,1252)Target_column




Tuesday, 20 September 2016

[Solved] ODI Error while sending mail using Jython code.Caused By: org.apache.bsf.BSFException: exception from Jython: SyntaxError: ("mismatched character '\\n' expecting '''",

We configured ODI send mail functionality using jython code as we have to configure authenticated mail functionality and also specify the port,

Jython code that we used for ODI Send mail.

import smtplib
import java.lang.String
import string
import java.lang as lang
BODY=string.join((
"To: %s" % 'User_Mailid',
"Subject: %s" % 'Mail Subject' ,
"",
'We used a variable for Mail Content'
), "\r\n")
sender = smtplib.SMTP('Mail Host',Port)
sender.set_debuglevel(1)
sender.ehlo()
sender.starttls()
sender.ehlo()
sender.login('Sender mail id','Password)
sender.sendmail('Sender mail id',['User_Mailid'],BODY)
sender.close()

When we executed the procedure for ODI- send mail functionality we got an error as shown in the screen shot.

Error:



Cause: Some mismatched character in the mail content.

Solution:Issue is with the variable that we used to get the count of source and target file count.

We used a refresh variable to get the count .

Issue is with the syntax that used.

we used chr(13)||chr(10) for new line in the variable and jython code is not supporting this type syntax so we replaced that with '\n'  then refreshed the variable and executed the package successfully.





Tuesday, 6 September 2016

Not able to give shared location for RPD. After configuring horizontal clustering in OBIEE [Caused by: oracle.sysman.emSDK.app.exception.EMSystemException ].

Error:

After Configuring horizontal clustering in OBIEE we are not able to give shared location for RPD in Enterprise Manager.

Solution :

Enabled global cache in Enterprise Manager and provided the shared path for global cache.

Cause:

In a clustered environment, Oracle BI Servers can be configured to access a shared cache that is referred to as the global cache.
This parameter specifies the physical location for storing cache entries shared across clustering.
This path must point to a network share. So that all clustering nodes share the same location.