Guru Of Geeks

#!/bin/sh #chkconfig: 345 99 10 # Start and stop Oracle Business Intelligence 11g components.  #  #   #  ORACLE_OWNR=obiee                                     # Local Unix user running OBIEE  ORACLE_FMW=/opt/MiddlewareHome          # Deployment Middleware directory  BIEE_DOMAIN=bifoundation_domain                        # Domain name  BIEE_INSTANCE=instance1                                # Instance name  BIEE_SERVER=bi_server1                                 # Server name  BIEE_MANAGER_URL=localhost:7001                       # Admin server URL (hostname:port)  BIEE_USER=weblogic                                     # Admin user  BIEE_PASSWD=password                                  # Admin password  LOG_PATH=/home/obiee/logs                             # Log directory  WL_PATH=$ORACLE_FMW/wlserver_10.3/server/bin  BIEE_PATH=$ORACLE_FMW/user_projects/domains/$BIEE_DOMAIN/bin  ORACLE_INSTANCE=$ORACLE_FMW/instances/$BIEE_INSTANCE  export ORACLE_INSTANCE  ORACLE_HOME=$ORACLE_FMW/Ora...

Problem(Abstract) A DataStage job does not use the new value that is put in the Parameter set. Cause If you make any changes to a parameter set object, these changes will be reflected in job designs that use this object up until the time the job is compiled. The parameters that a job is compiled with are the ones that will be available when the job is run (although if you change the design after compilation the job will once again link to the current version of the parameter set). Diagnosing the problem Examine the log entry "Environment variable settings" for parameter sets. If the parameter set specifies the value "(As predefined)", the parameter set is using the value that was used during the last compile. Resolving the problem If the value of the parameter set may be changed, you should specify a Value File for the parameters or set the parameters in the parameter set (including encrypted parameters) to $PROJDEF. Source:  http://www-01.ibm.com/support/docview.ws...

Delete files older than 30 days 1 find . - mtime + 30 - exec rm { } \ ; 1. Save the deleted files to a log file 1 find / home / a - mtime + 5 - exec ls - l { } \ ; > mylogfile .log This way, you'll get a line at top with the date the line is executed (also a line at the bottom). The last two semicolons are necessary, one is for find and one for bash. 2. modified Find and delete files modified in the last 30 minutes 1 find / tmp / - type f - mmin 30 - exec rm { } \ ; mtime = days mmin = minutes 3. force force delete temp files older then 30 days 1 find / tmp - mtime + 30 - exec rm - f { } \ ; 4. move the files move files older than 30 days to an archive folder – and preserve path strcuture 1 find / tmp - mtime + 30 - exec mv - t { } / archive / directory / \ ; mv -t: ensure directory structure is preserved References 1. Source of Tips:  http://www.howtogeek.com/howto/ubuntu/delete-files-older-than-x-days-on-linux/ 2. Using the find comma...

When you execute a job, the generated OSH and contents of the configuration file ($APT_CONFIG_FILE) is used to compose a "score". This is similar to a SQL query optimization plan. At runtime, IBM InfoSphere DataStage identifies the degree of parallelism and node assignments for each operator, and inserts sorts and partitioners as needed to ensure correct results. It also defines the connection topology (virtual data sets/links) between adjacent operators/stages, and inserts buffer operators to prevent deadlocks (for example, in fork-joins). It also defines the number of actual OS processes. Multiple operators/stages are combined within a single OS process as appropriate, to improve performance and optimize resource requirements. The job score is used to fork processes with communication interconnects for data, message and control3. Processing begins after the job score and processes are created. Job processing ends when either the last row of data is processed by the final op...