Error - mongod shell doesn't start, /data/db doesn't exsist

Error - mongod shell doesn't start, /data/db doesn't exsist


If you face this error while starting MongoDB (mongod), most probably there are 2 reasons for this -

a.  /data/db is not exist at all
b. mongod process don't have access on /data/db

Solution :-

The default db path for mongodb is /data/db/.
So when you run:

MongoDB is unable to start due to lock file

While starting MongoDB server, You are facing that MongoDB is not getting up with a exception says -

Sun Jan 18 12:27:03.884 [initandlisten] exception in initAndListen: 10310 Unable to lock file: /data/db/mongod.lock. Is a mongod instance already running?, terminating
Sun Jan 18 12:27:03.884 dbexit:

Normally, we are facing this issue due to 1. improper MongoDB server shutdown or 2. someone else is started the mongo server. In the second case, we dont have any issue, we can connect to out db without issue.

Conductor Node in Datastage

Below is the sample APT CONFIG FILE ,see in bold to mention conductor node.


{
node "node0"
{
fastname "server1"
pools "conductor"
resource disk "/datastage/Ascential/DataStage/Datasets/node0" {pools "conductor"}
resource scratchdisk "/datastage/Ascential/DataStage/Scratch/node0" {pools ""}
}

WebSphere Application Server[WAS] fails to start in Linux

The application server fails to start after system is restarted. No messages are generated in the application server logs.

The Metadata server startup script fails to finish. You must issue the nohup command for the Metadata server startup script.

Check to ensure that WebSphere Application Server is running.

To connect to the application server using an Internet browser:

1. Start your Internet browser.
2. Type the application server address in the form: http//isserver:portnumber, where isserver is the name of the computer where the services tier is installed or its tcp/ip address, and portnumber is the port for connecting to the services tier (by default, 9080).

If the application server has started, the login screen is displayed; otherwise an error message is displayed.

Teradata Users

 In Teradata, a user is the same as a database with one exception. A user is able to logon to the system and a database cannot. Therefore, to authenticate the user, a password must be established. The password is normally established at the same time that the CREATE USER statement is executed. 

The password can also be changed using a MODIFY USER command.

DataStage Macros Example

Job Design :
 

DataStage Macros

They are built from Data Stage functions and do not require arguments.

A number of macros are provided in the JOBCONTROL.H file to facilitate getting information about the current job, and links and stages belonging to the current job. These can be used in expressions, job control routines, filenames and table names, and before/after subroutines.

Some Parallel transformer Macros are listed here, as said, these can be used in anywhere in job

Failure to connect to DataStage services tier: invalid host name

When you attempt to start one of the Datastage clients, the following message is displayed:

Failed to authenticate the current user against the selected

Domain: Server [servername] not found.

Checks & Solution :

You might be specifying an incorrect name for the computer that is hosting the services tier.

You can check whether the application server is running by attempting to connect to the application server using an Internet browser.

Issuing commands to a Queue Manager (runmqsc)

Once we have created a Queue Manager, we will want to perform administrative tasks, such as creating queues, among others. To enable us to communicate with our Queue Manager, we use the RUNMQSC MQ command, which opens the MQSC (MQ Script Center) environment.

After entering the MQSC environment, we can issue one of the following MQSC commands: ALTER, CLEAR, DEFINE, DELETE, DISPLAY, END, PING, REFRESH, RESET, RESOLVE, RESUME, START, STOP, or SUSPEND. Each of these commands has it's own options, which are shown in the following table:

Stopping and Starting Oracle 11g Database Services in Windows

There are lot of services consuming a lot of CPU when an Oracle DB is running on machine. If you are using Oracle for learning/testing purpose only then you do not want to keep it up all the time.

So, here I am sharing 2 batch files for Stopping & Starting the Oracle Services on Windows which can do your work in one click only...

datastage4you QAnT - April2013 - 2

Click here ---> datastage4you QAnT - April2013 - 1

#14. DataStage Server – starting the server
a) DB2
su - db2inst1 -c "db2start“
b) WAS Server
/opt/IBM/WebSphere/AppServer/bin/startServer.sh server1 -user wasadmin -password PASSWORD
c) NODE
/opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh start
d) Engine
/opt/IBM/InformationServer/Server/DSEngine/bin/uv -admin -start

datastage4you QAnT - April2013 - 1

 #1. Use the Data Set Management utility, which is available in the Tools menu of the DataStage Designer or the DataStage Manager, to examine the schema, look at row counts, and delete a Parallel Data Set. You can also view the data itself.

#2. Use Sort stages instead of Remove duplicate stages. Sort stage has got more grouping options and sort indicator options.

#3. for quick checking if DS job is running on Server or not from UNIX
ps -ef | grep 'DSD.RUN'

Start/Stop/Delete a Queue Manager

Starting a Queue Manager

Before we can use a Queue Manager, we need to start it, using the STRMQM command. The command to start a Queue Manager called QMA is:

$ strmqm QMA

You should see output similar to the following on your screen:

WebSphere MQ queue manager 'QMA' starting.

2108 log records accessed on queue manager 'QMA' during the log replay phase.

Log replay for queue manager 'QMA' complete.

Transaction manager state recovered for queue manager 'QMA'.

WebSphere MQ queue manager 'QMA' started.

Create/start/stop a Queue Manager

To create a Queue Manager, our userID needs to be part of the mqm group. If we do not have the appropriate authority, then we need to ask our MQ administrator to issue this command.

The command to create a Queue Manager is CRTMQM and there are various parameters available with this command:

crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]

[-g ApplicationGroup] [-t TrigInt]

[-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec]

[-lc | -ll] [-lf LogFileSize] [-ld LogPath] QMgrName

DataStage Unix processes

Following are unix process list for a healthy DS system (Engine + Services + Metadata repository)

Process: /opt/IBM/InformationServer/ASBNode/apps/jre/bin/java Class: com.ascential.acs.logging.agent.LoggingAgentSocketImpl

Clean ReStart of the IBM InfoSphere DataStage Engine

If you suspect some Client sessions did not cleanly end or disconnect, you can perform a clean restart to make sure the DataStage Engine is starting from scratch. Please make sure all clients are logged off and no jobs are running before performing the below steps.

Here are the instructions for a clean restart of DataStage Engine:

Speed up your Lotus Notes performance by tuning the JVM

Lotus Notes uses Java Virtual Machine (JVM) for processing of Lotus Notes applications and plugins. 

IBMs Lotues Notes client configuration has a standard value that defines how many megabytes of RAM Lotus Notes can maximally use for JVM. This value is for PCs with above 1 GB RAM initially set too low, as it should be approx. 1/3 of the RAM of the PC (default value = 256 MB, but should be 768 MB).

Starting DataStage from batch[bat] file in Windows

Hi there..
I am going to share a small bat[batch] script which can be used to start the DataStage server in
 windows environment,

put this bat file in DSHOME or u can add a line in script to cd to DSHOME..

Stopping and starting the DataStage server engine

Restart the IBM InfoSphere Information Server engine whenever you complete certain tasks such as editing the dsenv file on Linux or UNIX or modifying the uvconfig file.

• Unix :
  

1.    Log in to the engine tier computer as the IBM InfoSphere DataStage® administrator (typically dsadm).

2.    Change to the engine directory and set the environment.

3.  cd $DSHOME

. ./dsenv

Starting and stopping WebSphere Application Server profiles

Starting a WebSphere Application Server profile

On Windows

To start a WebSphere Application Server profile, use any of these methods:

·         Go to Start > Programs > IBM WebSphere > Application Server V7.0 > Profiles > profile_name > Start the server.

·         Start the Windows service associated with the IBM WebSphere Application Server V7.0 profile.

·         Run this command: was_install_dir\bin\startServer.bat server1 –profileName profile

·         Run this command: profile_dir\bin\startServer.bat server1