Monday, 13 September 2021

Wednesday, 28 July 2021

How to Audit and Monitor BI Publisher Reports Access

Enable Auditing related properties in BI Publisher configuration file

1.     Open xmlp-server-config.xml file, which is located under $BI_HOME/ user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Configuration directory.

2.    Set the following three properties values to ‘true’.

·  AUDIT_ENABLED

·  MONITORING_ENABLED

·  AUDIT_JPS_INTEGRATION

The ‘AUDIT_JPS_INTEGRATION’ is not in the file as default, so you need to add this. Here is an example of how it looks for the xmlp-server-config.xml file after the modification.

 <?xml version="1.0" encoding="UTF-8" standalone="no"?><xmlpConfigxmlns="http://xmlns.oracle.com/oxp/xmlp">

<property name="SAW_SERVER" value="adc6160510"/>

<property name="SAW_SESSION_TIMEOUT" value="90"/>

<property name="DEBUG_LEVEL" value="exception"/>

<property name="SAW_PORT" value="7001"/>

<property name="SAW_PASSWORD" value=""/>

<property name="SAW_PROTOCOL" value="http"/>

<property name="SAW_VERSION" value="v6"/>

<property name="SAW_USERNAME" value=""/>

<property name="SAW_URL_SUFFIX" value="analytics/saw.dll"/>

<property name="MONITORING_ENABLED" value="true"/>

<property name="MONITORING_DEFAULT_HISTORY_SIZE" value="30"/>

<property name="AUDIT_ENABLED" value="true"/>

<property name="JSESSION_RESET_DISABLED" value="true"/>

<property name="SECURITY_MODEL" value="ORACLE_AS_JPS"/>

<property name="AUDIT_JPS_INTEGRATION" value="true"/>

</xmlpConfig>

 

Copy component_events.xml file to Audit Framework’s location

There is a Audit related configuration file provided by BI Publisher that needs to be copied to the Audit Framework location.

1.     Go to the following directory.

$BI_HOME /oracle_common/modules/oracle.iau_11.1.1/components

Create a directory called ‘xmlpserver’

Copy component_events.xml file from

/user_projects/domains/bifoundation_domain/config/bipublisher/repository/Admin/Audit

To

the newly created ‘xmlpserver’ directory.

Enable Auditing Policy with Fusion Middleware Control (EM)

Now you can set a level of the auditing for each BI Publisher’s auditing type by using Fusion Middleware Control (a.k.a. Enterprise Manager).

1.     Login to Fusion Middleware Control UI

http://hostname:port/em (e.g. reporting.oracle.com:7001/em)

2.     Access to Audit Policy configuration UI from the menu

Under WebLogic Domain, right-click bifoundation_domain, select Security and then click Audit Policy.



 

3.     Set Audit Level for BI Publisher.

While you can select ‘Custom’ to set a customized level of Auditing for each component, I’m selecting ‘Medium’ for this exercise.

Restart WebLogic Server

After all the above settings, now you need to restart the WebLogic Server instance in order to take those changes in effect. If you’re on Windows you can simply do this by selecting ‘Stop BI Servers’ and ‘Start BI Servers’ from the Start menu.


If you’re on Linux then you can run ‘stopWebLogic.sh’ and ‘startWebLogic.sh’, which can be found under $BI_HOME/user_projects/domains/bifoundation_domain/bin

Start Auditing!

Now assuming that you have completed the above steps successfully, then from this point on any reporting activity should be audited and stored in the auditing log file, which can be found at $BI_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/auditlogs/xmlpserver/audit.log

or 

$BI_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/auditlogs/xmlpserver/audit.log

Wednesday, 14 July 2021

Oracle database 11.2.0.4 download link

 Login to support.oracle.com

Go to Patches & updates tab 

Enter Patch Number 13390677 and select Platform

Click search






Download








File 1&2 is db, 3 is grid, 4 is client, 5 is gateway, 6 is example, 7 is deinstall








The selected Oracle database is not configured to use the AL32UTF8 character set

 While running the RCU, below error comes if the database is not configured to use the AL32UTF8 character set -

bild-28

In order to change the character set in the database, follow the next steps.

1. Open SQLplus and login using a sysdba role

2. One by one, execute the next statements.

shutdown immediate;
startup restrict;
alter database character set internal_use AL32UTF8;
alter database character set AL32UTF8;
shutdown immediate;
startup;
3. Exit SQL Plus

Thursday, 27 May 2021

How to connect to Sales Force (SFDC) From Informatica

 

In order to connect to Sales Force.com. Power Exchange SFDC  needs to be installed and  sfdc plug-in needs to be registered in Informatica Repository.Below are the steps for the same.



  1. Log on to server as Informatica functional account.
  2. Change directory to Informatica PowerCenter install binaries directory.
  3. Ftp/Sftp sfdc_81102_sol32.tar from either local workstation or Informatica server to server where install is taking place
  4. Decompress install binaries  (tar xvf sfdc_81102_sol32.tar).
  5. At this point, stop integration service and repository service in the environment using admin console.
  6. Execute installSFDCserver.
  7. Enter Informatica home directory absolute path ($INFA_HOME).
  8. Once installation has completed, return to admin console.
  9. Add license key to environment using admin console.
  10. Select the respective Unicode integration service, modify the HTTP Proxy Properties as follows: HttpProxyServer  ,HttpProxyPort , HttpProxyUser, HttpProxyPassword, HttpProxyDomain.










  • Start repository service.
  • Start integration service.
  • Log into repository using Workflow manager.
  • Validate that salesforce.com connection is now an option under application type connections in workflow manager.
  • Log into repository using Designer.
  • Validate that you can import a source from salesforce.com, and that it is now an option in source analyzer.
  • If both workflow manager and designer allow these options, installation is complete.

     Below Is the Installation Output :

    $INFA_HOME/server/tomcat/bin/SFDC_81102_Sol32

    Stop all the Powercenter processes/Services before running this script ....
    Enter absolute path of Powercenter server installation directory{/home/powercenter8.1.1}
    $INFA_HOME
    server location:$INFA_HOME
    backing up $INFA_HOMEserver/bin/native/pmsfdc.xml as $INFA_HOME/server/bin/native/pmsfdc.xml.bak
    copying files to $INFA_HOMEserver/bin/native folder
    backing up $INFA_HOMEserver/bin/libpmsfdccmn.so as $INFA_HOME/server/bin/libpmsfdccmn.so.bak
    backing up $INFA_HOMEserver/bin/libpmsfdclkp.so as $INFA_HOME/server/bin/libpmsfdclkp.so.bak
    backing up $INFA_HOMEserver/bin/libpmsfdcrdr.so as $INFA_HOME/server/bin/libpmsfdcrdr.so.bak
    backing up $INFA_HOMEserver/bin/libpmsfdcwrt.so as $INFA_HOME/server/bin/libpmsfdcwrt.so.bak
    backing up $INFA_HOMEserver/bin/pmsfdc_EN.cat as $INFA_HOME/server/bin/pmsfdc_EN.cat.bak
    backing up $INFA_HOMEserver/bin/pmsfdc_JA.cat as $INFA_HOME/server/bin/pmsfdc_JA.cat.bak
    copying files to $INFA_HOMEserver/bin folder
    cp: server/bin/native: is a directory
    Installation completed successfully.
    IMPORTANT: If you are upgrading from 8.1.1 please re-register the Salesforce.com plug-in pmsfdc.xml for changes to take effect.
     
     Below are the steps to register the sfdc plugin to Repository :
    • Get the pmsfdc.xml from Informatica Vendor.
    • FTP the pmsfdc.xml file in binary mode and place it to Informatica server $INFA_HOME/server/bin/native/ path. (Make sure to FTP the sfdc plug in binary mode).
    • Bring down the Integration Service.
    • Bring the repository service to Exclusive mode from Normal mode. 
    • Connect to the repository using the pmrep connect command.
                  pmrep>connect -r "LAB_INFA_REP" -d "LAB_INFA_DOMAIN" -n Administrator -x password
    • Now register the plugin using the registerplugin command.
                 pmrep>registerplugin -i $INFA_HOME\server\bin\native\pmsfdc.xml -e -N 
    (Note : Give the fully qualified path otherwise will get the above error Failed to execute registerplugin )

    Register Plug-in operation on repository [LAB_INFA_REP] started at **/**/**** 00:00:00.

    Importing plugin: SalesforcePlugin ...
    Importing dbtype: Salesforce ...
    Importing keytype: SOURCEID ...
    Importing keytype: TARGETID ...
    Importing keytype: SOURCEREFERENCE ...
    Importing keytype: TARGETREFERENCE ...
    Importing datatype: id ...
    Importing datatype: id ...
    Importing datatype: id ...
    Importing datatype: id ...
    Importing datatype: id ...
    Importing datatype: id ...
    Importing datatype: id ...

    Post validation on imported plug-ins...
    The number of plug-ins that registered successfully is 1.
    The number of plug-ins that failed to register is 0.
    Register Plug-in operation on repository [
    LAB_INFA_REP] ended at **/**/**** 00:00:00. Elapsed time is 0:00:03.
    registerplugin completed successfully.
    pmrep>exit

    Thursday, 28 January 2021

    Authentication denied: Boot identity not valid (OBIEE service startup issue)

     

    If getting any of the below error in log–

    <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid.

    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic denied

    <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid.

    Authentication denied: Boot identity not valid

    Then check the boot.properties file under security folder and data/nodemanager folder if they have been changed recently, edit boot.properties and change the password.

    Boot.properties location –

    /<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/AdminServer/security/boot.properties

    /<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/security/boot.properties

    /<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/data/nodemanager/boot.properties 

    Backup and remove ldap folder from -

     /<MiddlewareHome>/user_projects/domains/bifoundation_domain/servers/bi_server1/data/

    OBIEE services Start/Stop script

    =========================================================================

                                                                Stop services

    =========================================================================

    ---------------------------------Step 1 Stop OPMN Components-----------

    If its a clustered environment then stop opmnctl in all nodes.

    cd /<MiddlewareHome>/instances/instance1/bin

    ./opmnctl stopall

    (wait until the prompt is back)

    --------------------------------Step 2 Stop Node Manager---------------

    If its a clustered environment then kill the process in all nodes.

    ps -ef |grep NodeManager

    kill -9 <number of process above>

    --------------------------------Step 3 Stop Managed Server---------------

    cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

    ./stopManagedWebLogic.sh <bi server name>

    eg.- ./stopManagedWebLogic.sh bi_server1

    If its a clustered environment -

    ./stopManagedWebLogic.sh bi_server1 t3://weblogic.hostServerNname:7001

    ./stopManagedWebLogic.sh bi_server2 t3://weblogic.hostServerName:7001

    If boot.properties are not set then provide user and password in the argument -

    ./stopManagedWebLogic.sh bi_server1 t3://obieenode1.com:7001 weblogic password

    ./stopManagedWebLogic.sh bi_server2 t3://obieenode1.com:7001 weblogic password

    Verify that the Managed Server has shutdown completely in both nodes with -

    ps -ef | grep bi_server1

    ps -ef | grep bi_server2

    -------------------------Step 4 Stop Admin Server------------------

    Only in node1-

    cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

    ./stopWebLogic.sh

    If boot.properties are not set then provide user and password in the argument -

    ./stopWebLogic.sh weblogic password t3://obieenode1.com:7001

    (wait until the prompt is back)

    ------------------------Kill any running processes----------------------------

    Check if any process is running in all nodes. 

    ps -ef | grep -v grep | grep -i weblogic.NodeManager

    ps -ef | grep Node | grep nodemanager | grep -v grep | cut -c10-15

    ps -ef | grep AdminServer


    =========================================================================

                                                                  Start Services

    =========================================================================

    -------------------------Step 1 Start Admin Server------------------

    only on node1 -

    cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

    nohup ./startWebLogic.sh &

    tail -1000f nohup.out

    or - log path can be provided -

    nohup ./startWebLogic.sh > /service_logs_path/startWeblogic.log 2>&1 &

    tail -1000f /service_logs_path/startWeblogic.log

    or - if boot.properties are not set then provide user and password in the argument -

    nohup ./startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startWeblogic.log 2>&1 &

    tail -1000f /service_logs_path/startWeblogic.log

    Output -

    <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

    --------------------------------Step 2 StartNode Manager---------------

    If its a clustered environment then run on all nodes.

    cd /<MiddlewareHome>/wlserver_10.3/server/bin/

    nohup ./startNodeManager.sh &

    tail -1000f nohup.out

    or - log path can be provided -

    nohup ./startNodeManager.sh > /service_logs_path/startNodeManager.log 2>&1 &

    tail -1000f /service_logs_path/startNodeManager.log

    Output -

    <Info> <Secure socket listener started on port ####>

    -----------------------------------Step 3 Start Managed Server------------

    cd /<MiddlewareHome>/user_projects/domains/bifoundation_domain/bin/

    nohup ./startManagedWebLogic.sh bi_server1 &

    tail -1000f nohup.out

    or - log path can be provided -

    nohup ./startManagedWebLogic.sh bi_server1 > /service_logs_path/startManagedWebLogic.log 2>&1 &

    tail -1000f /service_logs_path/startManagedWebLogic.log

    If its a clustered environment then (obieenode1 is node1_hostname) -

    nohup ./startManagedWebLogic.sh bi_server1 t3://obieenode1:7001 &

    nohup ./startManagedWebLogic.sh bi_server2 t3://obieenode1:7001 &

    nohup -1000f nohup.out

    or - if boot.properties are not set then provide user and password in the argument -

    nohup ./startManagedWebLogic.sh bi_server1 t3://obieenode1:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startManagedWebLogic.log 2>&1 &

    nohup ./startManagedWebLogic.sh bi_server2 t3://obieenode1:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=password > /service_logs_path/startManagedWebLogic.log 2>&1 &

    nohup -1000f /service_logs_path/startManagedWebLogic.log

    Output-

    Server started in RUNNING mode

    ---------------------------------Step 4 Startup OPMN Components-----------

    If its a clustered environment then run on all nodes.

    cd /<MiddlewareHome>/instances/instance1/bin

    ./opmnctl startall

    Check status -

    ./opmnctl status

    Output -

    ------------------------------------+-------------------------+----------+---------

    ias-component                         | process-type              |    pid      | status

    ------------------------------------+-------------------------+----------+---------

    coreapplication_obisch1          | OracleBIScheduler~  |    xxxx | Alive

    coreapplication_obiccs1          | OracleBIClusterCo~  |    xxxx | Alive

    coreapplication_obips1            | OracleBIPresentat~   |    xxxx | Alive

    coreapplication_obijh1            | OracleBIJavaHostC~ |    xxxx | Alive

    coreapplication_obis1             | OracleBIServerCom~ |    xxxx | Alive


    Start any particular opmnctl component -
    ./opmnctl startproc ias-component=coreapplication_obisch1

    or stop -
    ./opmnctl stopproc ias-component=coreapplication_obisch1


    Friday, 23 August 2019

    How to reset Weblogic password

    If you have lost the Weblogic password or want to chnage the password then this post will help you to change the Weblogic password.

    1. Make sure all the services are down

    2. change directory to <Middleware_Home>\user_projects\domains\bifoundation_domain\bin

              cd <Middleware_Home>\user_projects\domains\bifoundation_domain\bin

    3. Set the setDomainEnv.cmd(Windows) / setDomainEnv.sh (Linux) script to set the Weblogic variables

               In windows: setDomainEnv.cmd

               In Linux: ./setDomainEnv.sh

    4. Now change the directory to security directory in your instance.

               cd <Middleware_Home>\user_projects\domains\bifoundation_domain\security

    5. Move the DefaultAuthenticatorInit.ldift to a backup file

              In Windows: move DefaultAuthenticatorInit.ldift DefaultAuthenticatorInit_old.ldift

              In Linux: mv DefaultAuthenticatorInit.ldift DefaultAuthenticatorInit_old.ldift

    6. Run the “java weblogic.security.utils.AdminAccount newuser newpassword .” to generate a new DefaultAuthenticatorInit.ldift with a new user with the assigned password within the security directory

             eg: java weblogic.security.utils.AdminAccount weblogic weblogic123 .

    Note: Ensure the password is a minimum of 8 characters and contains at least one numeric character. Also, don’t forget the dot “.” at the end of the above command, it is required.

    7. Change directory to <Middleware_Home>\user_projects\domains\bifoundation_domain\servers\AdminServer\security

              cd <Middleware_Home>\user_projects\domains\bifoundation_domain\servers\AdminServer\security\

    8. Edit the boot.properties file and remove password and username

            password=

            username=

    The boot.properties will get encrypted with new username and password once the admin server starts up

    9. Rename or remove directory <Middleware_Home>\user_projects\domains\bifoundation_domain\servers\AdminServer\data\ldap as it will get recreated once the WebLogic Admin server starts.

           e.g: rename Middleware_Home>\user_projects\domains\bifoundation_domain\servers\AdminServer\data\ldap_old

    10. Change directory to <Middleware_Home>\user_projects\domains\bifoundation_domain\bin and start the Weblogic Admin Server

    In Windows: startWebLogic.cmd

    In Linux:  ./ startWebLogic.sh

    11. Once the weblogic server is up, you’ll be able to login to Console with the new weblogic Admin user and password.

    Thursday, 30 March 2017

    OBIEE 11g Config and log file locations

    bi_server1.log  &  bi_server1-diagnostic.log 
    [$FMW_HOME]/user_projects/domains/bifoundation_domain/servers/bi_server1/logs
    nqserver.log    &    nqquery.log
    [$FMW_HOME]/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1
    sawlog.log
    [$FMW_HOME]/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1
    NQSConfig.INI   &  DBFeatures.INI
    [$FMW_HOME]/instances/instance1/config/OracleBIServerComponent/coreapplication_obis1
    instanceconfig.xml      &     credentialstore.xml
    [$FMW_HOME]/instances/instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips1
    config.xml
    [$FMW_HOME]/user_projects/domains/bifoundation_domain/config
    system-jazn-data.xml
    [$FMW_HOME]/user_projects/domains/bifoundation_domain/config/fmwconfig

    Tuesday, 28 February 2017

    mount windows folder in linux

    mount -t smbfs -o username=pc,password=**** /home/mount-point //192.168.1.15(Windows folder path)

    BASIC UNIX COMMANDS

    1. tty - reveals the current terminal
    2. whoami - reveals the currently logged-in user
    3. which - reveals where in the search path a program is located
    4. echo - prints to the screen
     a. echo $PATH - dumps the current path to STDOUT
     b. echo $PWD - dumps ths contents of the $PWD variable
     c. echo $OLDPWD - dumps the most recently visited directory

    5. clear - clears the screen or terminal
    6. history - reveals your command history
     a. command history is maintained on a per-user basis via:
      ~/.sh_history
    ~ = users's $HOME directory
    7. pwd - prints the working directory
    8. cd - changes directory to desired directory
     a. 'cd ' with no options changes to the $HOME directory
     b. 'cd ~' changes to the $HOME directory
     c. 'cd /' changes to the root of the file system
     d. 'cd ..' changes us one-level up in the directory tree
     e. 'cd ../..' changes us two-levels up in the directory tree

    9. ls - lists files and directories
     a. ls / - lists the contents of the '/' mount point
     b. ls -l - lists the contents of a directory in long format:
     Includes: permissions, links, ownership, size, date, name
     c. ls -ld /etc - lists properties of the directory '/etc', NOT the contents of '/etc'
     d. ls -ltr - sorts chronologically from older to newer (bottom)
     e. ls -a - reveals hidden files. e.g. '.sh_history'
    Note: files/directories prefixed with '.' are hidden. e.g. '.sh_history'

    10. cat - catenates files
     a. cat 123.txt - dumps the contents of '123.txt' to STDOUT
     b. cat 123.txt 456.txt dumps both files to STDOUT
     c. cat 123.txt 456.txt > 123456.txt - creates new catenated file

    11. mkdir - creates a new directory
     a. mkdir test - creates a 'test' directory

    12. cp - copies files
     a. cp 123.txt test/

    13. mv - moves files
     a. mv 123456.txt test/ - moves the file, preserving timestamp

    14. rm - removes files/directories
     a. rm 123.txt
     b. rm -rf 456.txt - removes recursively and enforces

    15. touch - creates blank file/updates timestamp
     a. touch test.txt - will create a zero-byte file, if it doesn't exist
     b. touch 123456.txt - will update the timestamp
     c. touch -t 201003221530 123456.txt - changes timestamp

    16. stat - reveals statistics of files
     a. stat 123456.txt - reveals full attributes of the file

    17. find - finds files using search patterns
     a. find / -name 'fstab'
    Note: 'find' can search for fields returned by the 'stat' command

    18. alias - returns/sets aliases for commands
     a. alias - dumps current aliases
     b. alias copy='cp'


    ###Unix Redirection & Pipes###
    Features:
     1. Ability to control input and output

    Input redirection '<':
     1. cat < 123.txt
    Note: Use input redirection when program does NOT default to file as input

    Output redirection '>':
     1. cat 123.txt > onetwothree.txt
    Note: Default nature is to:
     1. Clobber the target file
     2. Populate with information from input stream


    Append redirection '>>':
     1. cat 123.txt >> numbers.txt - creates 'numbers.txt' if it doesn't exist, or appends if it does

     2. cat 456.txt >> numbers.txt


    Pipes '|':
    Features: Connects the output stream of one command to the input stream of a subsequent command

     1. cat 123.txt | sort
     2. cat 456.txt 123.txt | sort
     3. cat 456.txt 123.txt | sort | grep 3


    ###Command Chaining###
    Features:
     1. Permits the execution of multiple commands in sequence
     2. Also permits execution based on the success or failure of a previous command

     1. cat 123.txt ; ls -l - this runs first command, then second command without regards for exit status of the first command

     2. cat 123.txt && ls -l - this runs second command, if first command is successful
     3. cat 1234.txt && ls -l

     4. cat 123.txt || ls -l - this runs second command, if first command fails


    20. more|less - paginators, which display text one-page @ a time
     1. more /etc/fstab
     2. less 1thousand.txt

    21. seq - echoes a sequence of numbers
     a. seq 1000 > 1thousand.txt - creates a file with numbers 1-1000

    22. su - switches users
     a. su - with no options attempts to log in as 'root'

    23. head - displays opening lines of text files
     a. head /var/log/messages

    24. tail - displays the closing lines of text files
     a. tail /var/log/messages

    25. wc - counts words and optionally lines of text files
     a. wc -l /var/log/messages
     b. wc -l 123.txt

    26. file - determines file type
     a. file /var/log/messages


    ###Tar, Gzip###
    Features:
     1. Compression utility (gzip)
     2. File roller (the ability to represent many files as one - tar)


    Gzip:
    Includes:
     1. gzip - compresses/decompresses files
     2. gunzip - decompresses gzip files

    Tasks:
     1. compress '1million.txt' file using gzip
      a. gzip -c 1million.txt > 1million.txt.gz

    Note: gzip auto-dumps to STDOUT, by default

      b. gzip -l 1million.txt.gz - returns status information
      c. gunzip 1million.txt.gz - dumps to file, and removes compressed version
      d. gzip -d 1million.txt.gz
      e. zcat 1million.txt.gz - dumps the contents to STDOUT
      f. less 1million.txt.gzip - dumps the contents of gzip files to STDOUT


    Tar :

     1. tar -cvf filename.tar path/ - creates a non-compressed archive
     2. tar -cvf 1million.txt.tar 1million.txt

    ###GREP###
    Features:
     1. The ability to parse lines based on text and/or RegExes
     2. Post-processor
     3. Searches case-sensitively, by default
     4. Searches for the text anywhere on the line


    1. grep 'linux' grep1.txt
    2. grep -i 'linux' grep1.txt - case-insensitive search
    3. grep '^linux' grep1.txt - uses '^' anchor to anchor searches at the beginning of lines
    4. grep -i '^linux' grep1.txt
    5. grep -i 'linux$' grep1.txt - uses '$' anchor to anchor searches at the end of lines

    Note: Anchors are RegEx characters (meta-characters). They're used to match at the beginning and end of lines

    6. grep '[0-9]' grep1.txt - returns lines containing at least 1 number
    7. grep '[a-z]' grep1.txt


    8. grep -v sshd messages - performs and inverted search (all but 'sshd' entries will be returned)
    9. grep -v sshd messages | grep -v gconfd

    Friday, 17 February 2017

    DAC errors and solutions while doing Full Load first time for the BI Apps (OBIA)

    Changes for the Errors :
    1.       SDE_ORA_GL_LinkageInformation_Extract
    Cause : Temp Tablespace Problem
    Solution : Added 30GB in Temp Tablespace in both (Apps and Datawarehouse) database for 1 year of data (Required more tempspace for more years of load)

    2.       SDE_ORA_GLSegmentDimension
    Error : Value larger than specified precision allowed for this column.
    Temp Solution : Alter column SEGEMENT_VAL_CODE size to 150 from 50.
    Solution : Check the SR for the solution

    3.       SDE_ORA_CodeDimension_FND_Flex_Mcat
    Error : 1- The Task was not added in Parameters file
                2- $$PROD_CAT_SET_ID1 - Inventry
    Solution : add the task to the parameter file (copy the other task parameter having similar name and paste it to the file with the required name).
    And $$PROD_CAT_SET_ID = 1 and $$INV_PROD_CAT_SET_ID = 1

    4.       SDE_ORA_EmployeeExpenseFact_FP_Full
    Need Patch on EBS – Patch 11i.FIN_PR/11i.OIE.I family Pack (Not required)
    Solution – Inactive Subject Area Employee Expense

    5.        SDE_ORA_PeggingDetailsFact and SDE_ORA_PeggingDetailsFact_ASCP
    Error : Invalid Identifier
    Solution : Inactive the Task

    6.       SDE_ORA_Project_Hierarchy and SDE_ORA_Project
    (Subjaect Are – Planing Analysis)
    Error : Invalid Identifier
    Solution : Inactive the Task

    7.       SIL_GLSegmentDimension
    Error : Index creation failed
    Solution : Create Index manually and mark the task as completed



    8.       Subject Area : Supply Chain – BOM Item
    Tasks : SDE_ORA_BOMHeaderDimension
                    SDE_ORA_BOMHeader_Auxillary
                    SDE_ORA_BOMItem_Fact
    ERROR : Invalid Identifier
    Solution : Patch required on EBS

    9.       SDE_ORA_ProductDimension_Derive_Full
    Error : Value too large
    Solution : Double the column length in mapping and in target table.

    10.   SDE_ORA_CustomerAccountDimension_Full
    Error : Value too large
    Solution : Double the column length in mapping and in target table.

    11.   SDE_ORA_SalesProductDimension_Full
    Error : Value too large
    Solution : Double the column length in mapping and in target table

    12.   SDE_ORA_CustomerFinincialProfileDimension_ProfileAmts_Full
    Error : Value too large
    Solution : Double the column length in mapping and in target table

    13.   SIL_BOM_ItemFact_Full
    Error : An error occurred executing the stored procedure
                    PLS – 00201 : identifier ‘COMPUTE_BOUNDS_ORA11i’ must be declared
    Solution : Navigate to the OracleBI\dwrep\Informatica\Stored_Procedure
                        Folder and copy the codes of COMPUTE_BOUNDS_ORA11i.sql and compile(run) into the
                        Dataware House database.

    14.   $$SET_OF_BOOKS_TYPE_LIST = ‘N’

    15.   Subject Area - SDE_ORA_ProductDimension_Full
    Task : SDE_ORA_ProductCategories_Resolve
    Error : [Error(transformation error)]
    Solution : Remove default value [Error(transformation error)] from port created_by_ID and change_by_ID from the update stratigy Upd_Strategy_W_ORA_Product_DS_Tmp_Ins_upd

    16.   SDE_ORA_GLBalanceFact
    Error : ORA-01488  Value larger than specified precision allowed for this column

    17.   SDE_ORA_UOMConversionGeneral_InterClass
    Cause : Taking long time to run (40-50 min) and then failing without any error
    Source table – MTL_UNITS_OF_MEASURE
                                    MTL_UOM_CLASS_CONVERSIONS


    Changes as per SR :
    Cause : Succeeded in Informatica monitor but failed in DAC
    Solution : Delete the Parameter $$YEAR_START from mappings and from the Tasks
    a.       PLP_ARXactGroupAccount_A2_Load
    b.      PLP_GLCogsGroupAccount_A2_Load
    c.       PLP_GLOtherGroupAccount_A2_Load
    d.      PLP_GLRevenGroupAccount_A2_Load

    How to set a OBIEE logging level

    You might want to diagnose performance or data issues by setting a temporary log level for a query. You can enable query logging for a specific query by preceding your Select statement with the following:
    Set Variable LOGLEVEL=n;
    This instruction sets the loglevel system session variable only for this SQL.
    See the following example:
    Set Variable LOGLEVEL=5; select year, product, sum(revenue) from time, products, facts
    For this query, the logging level of five is used regardless of the value of the underlying LOGLEVEL variable.
    Available in 11G
    You can find a default logging level in the option of the repository:

    This option determines the default query logging level for the internal BISystem user.
    A query logging level of 0 (the default) means no logging. Set this logging level to 2 to enable query logging for internal system processes likeevent polling and initialization blocks.
    By setting the loglevel system session variable via an initialization block, you can control the loglevel of each user.
    The loglevel must be an integer datatype
    The session variable LOGLEVEL overrides a user's logging level. For example, if the Oracle BI Administrator has a logging level defined as 4 and LOGLEVEL is defined as default 0 (zero) in the repository, the Oracle BI Administrator's logging level will be 0.
    §  In the Administration Tool, select Manage > Security (10g) or Identity (11g). The Security Manager dialog box appears.
    §  Double-click the user's user ID. The User dialog box appears.
    §  Set the logging level by clicking the Up or Down arrows next to the Logging Level field.


    You cannot configure a logging level for a group.