INSTALLATION DOCUMENTS BY RAVI

Monday, November 27, 2017

Steps for backup and restore informatica power center repository

Backup Informatica Power Center Repository:

1. Login to admin console and select repository service























2. Under Actions menu select Repository Contents and then click on Back Up




















3.  Give user name and password and specify the backup file name and click ok























4. After completing we can see the backup file in below location.


















Restore Informatica Power Center Repository:

1. Login to admin console and select repository service
2. Change the repository service operating mode to Exclusive and click ok ok and ok








































3. Under Actions menu select Repository Contents and then click on delete and give user name and password and click ok























4. Now Under Actions menu select Repository Contents and then click on restore.
5. Select the backup repository file to restore and click ok
6. Change the repository service operating mode from Exclusive to Normal

Steps for Restoring Informatica Power Center Repository on new machine:

1. Create a new schema for the new repository.
2. Create a new Repository Service (referencing the new database schema).
3. Select the Do not create content option.
4. Enable the new Repository Service. 
5. It will display a message stating that the repository does not have any content.
6. Restore the backup using this new Repository Service.
7. Enable the new Repository Service to confirm that the restore is successful. 
8. If the Repository Service will display a message indicating that an upgrade is required.
9. Select Action > Repository Contents > Upgrade. 
10. This will start the upgrade of the repository contents.
11. Change the repository mode from Exclusive to Normal.


Steps for backup and restore informatica domain

Backup Informatica Domain:

1. Stop all the informatica services and server








2. Backup the domain using infasetup BackupDomain command utility

Syntax:


infasetup.(bat | sh) BackupDomain -da <database_hostname:database_port> -du<database_user_name> -dp <database_password> -dt <database_type> -ds<database_service_name> -bf <backup_file_name> -dn <domain_name>










Check for the backup file
















Restoring Informatica Domain:

1. Copy the backup file to the new machine
2. Create a database schema and a user account in a supported database
3.  Install informatica on the new machine but do not configure 
4. Copy the files in the <INFA_HOME>/server/infa_shared directories on the original machine to the new machine.
5. Restore the domain configuration backup to the database schema.

Run the infasetup RestoreDomain command to restore the domain configuration in the backup file to the
specified database schema.

Syntax:

infasetup.(bat | sh) RestoreDomain -da <database_hostname:database_port> -du<database_user_name> -dp <database_password> -dt <database_type> -ds<database_service_name> -bf <backup_file_name>

6. Update the database connection information for each gateway node.Gateway nodes must have a connection to the domain configuration database to retrieve and update domain configuration. Run the infasetup Update Gateway Node command on each gateway node to update the database connection information for each gateway node.

Syntax:


infasetup.(bat | sh) UpdateGatewayNode -da <database_hostname:database_port> -du<database_user_name> -dp <database_password> -dt <database_type> -ds<database_service_name> -dn <domain_name>

7. Start all the nodes and enable all application services in domain

MySQL Daemon failed to start

When try to start the mysql database getting the below error:

"MySQL Daemon failed to start"





Try with the command mysql as below and check for the error





Here we get the error " Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' "

To resolve this error check the my.conf file under /etc folder















Here in my case bind address is different from my host ip address so I changed it to my host ip address and tried to start mysql again






Monday, November 20, 2017

Enable Root User on Ubuntu

1. Set password for root user:

Login as user
Open terminal
Issue the below command to set password for root user

$sudo passwd root

Give the password for root user 

2. Open the file 50-ubuntu.conf under the path (/usr/share/lightdm/lightdm.conf.d/)

Add the below line to it.

greeter-show-manual-login=true

Save and close the file.

3. Reboot the machine and now we can login as root user.





Saturday, November 18, 2017

OWB repository seeding failed

When we are working with owb repository assistant for the first time we may get the below error












To resolve this :

1. Connect to the database as sysdba user and run the remote_owb_install.sql and provide the OWB_REMOTE_ADMIN directory as below
















2. Execute the OWB scripting command to seed the repository

Navigate to $ORACLE_HOME/owb/bin/unix and open the shell ombplus by running the command OMBPlus.sh as below





Execute the below command to seed the OWB repository





3. Now relaunch the repository assistant and try to create workspace





Resolution : ORA-01157: cannot identify/lock data file 6 - see DBWR trace file

When we are working with oracle database some times the database may not open with the below errors:

ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'C:\APP\ADMINISTRATOR\ORADATA\ORCL\DEV_SVCTBL.DBF'














Solution:

To resolve this error issue the below sql commands and try to open the database

1. select name from v$datafile where file#=6;
2. alter database datafile 6 OFFLINE DROP;
3.alter database open;







When we try to open the database again we may get data file error






Repeat this step until all the error data files got dropped
Ones this got resolved we can open the database















Saturday, November 11, 2017

Step by step Apache Hadoop cluster configuration

 Prerequisites:
1.  Create number of nodes we want for clustering
2. Set ip and hostname on each node properly
3. Setup ssh connectivity between all the nodes and test it

COMMON CONFIGURATION FOR ALL NODES

UPDATE CORE-SITE.XML FILE (In all nodes):









































UPDATE HDFS-SITE.XML
On Master node:

























On slave nodes:
























UPDATE YARN-SITE.XML (all nodes):
















































UPDATE MAPRED-SITE.XML (on all nodes):














































Add or modify masters and slaves files on Name node only as below:















































FORMAT THE NAME NODE IN MASTER NODE ONLY:
Note: Do not format a running cluster because this will erase all existing data in the HDFS file system





















START THE CLUSTER:



















Now to check whether all daemons are running or not, type the following command: (In Master node)







Now to check whether all daemons are running or not, type the following command: (In Slave node)







REVIEW IN CONSOLE

If all the daemons started successfully in all nodes then you can see the nodes in the listed in the console.
You can type the following command in terminal and verify that:

Command > hadoop dfsadmin -report


























You can type the following url and verify that:










































Thursday, November 2, 2017

Steps for copying files between remote windows systems from command prompt using xcopy

1. We can copy the files between two windows systems using xcopy

2. Share a folder on target machine where we want to copy the files



















Right click on the folder
Select share with and then click on Specific people


















Add Everyone and set permission level to Read/Write
Click on Share


















Click on Done



















3. Source system folder





















4. On the source system open the command prompt as an administrator and run the below command to copy files between source and target

xcopy source_folder_path  \\target_hostname\target_folder_path  /E

























Here we got "Invalid drive specification" error
Note: To work with xcopy we need to map the network shared path at least ones or we need the access the shared folder ones from the source system
click windows + r button
In the resulting window typed the network shared path and click ok














Enter the username and password and click ok















Click ok





















Close it and again try to copy the files using xcopy

























Now open the target folder on remote system and check for the files




















  Opatch reports 'Cyclic Dependency Detected' error when patching ODI   Issue: When applying a Patch Set Update (PSU) to WebLogic Se...