Author Archives: Petr

[Salesforce.com] Regex too complicated

Working with the regular expressions in Salesforce.com is same as in the Java. But the regex have restrictions to its complexity. For example, this regex throws compilation error:

([a-zA-Z]*_*)*\.([a-zA-Z]*_*)*\.[0-9]*

1	([a-zA-Z]_)\.([a-zA-Z]_)\.[0-9]*

If you have to use multiple times the symbol * in your regex, the Salesforce.com evaluates your pattern as too complicated.

Workaround

The workaround is to use for example {0,9999} instead of *. Here is retyped first pattern, but without exception :)

([a-zA-Z]*_*)*\.([a-zA-Z]*_*){0,9999}\.[0-9]{0,9999}

1	([a-zA-Z]_)\.([a-zA-Z]_*){0,9999}\.[0-9]{0,9999}

Note: You can replace all asterisk. The value 9999 can be longer, for example 99999999 and everything will work in same way.

[Salesforce.com] Upsert on the User object

If you are trying to do the UPSERT operation on the User object, for example:

User theUser = new User();
...
theUser.FederationIdentifier = 'FederationIdentifier';

upsert theUser FederationIdentifier;

User theUser = new User();

...

theUser.FederationIdentifier = 'FederationIdentifier';

upsert theUser FederationIdentifier;

you will get error:

DML not allowed on User

1	DML not allowed on User

Workaround

The workaround for this case is use the Database object:

User theUser = new User();
...
theUser.FederationIdentifier = 'FederationIdentifier';

Database.upsert(theUser, User.Fields.FederationIdentifier, true);

User theUser = new User();

...

theUser.FederationIdentifier = 'FederationIdentifier';

Database.upsert(theUser, User.Fields.FederationIdentifier, true);

…and now you can happily use the upsert operation on the User object :)

Docker can’t connect to boot2docker (OSX)

When you are trying to connect docker to boot2docker on OSX, you probably got this error message:

fata 0032 an error occurred trying to connect i/o timeout

1	fata 0032 an error occurred trying to connect i/o timeout

Solution to fix this error:

Go to the Virtual Box -> Preferences -> Network -> Host-only networks

Delete the host only networks
and create one new.

Then open the command line run this commands:

Warning: The boot2docker command delete all your docker images!

> boot2docker delete
> boot2docker download
> boot2docker init
> boot2docker up
> (set the environment variables like DOOCKER_HOST etc.)
> docker info

> boot2docker delete

> boot2docker download

> boot2docker init

> boot2docker up

> (set the environment variables like DOOCKER_HOST etc.)

> docker info

Now, the docker could be works!

IBM Cognos: XQE-JDB-0004 A problem occurred finding the driver class “com.ibm.db2.jcc.DB2Driver”.

When you are trying to test the connection to the DB2 database from Cognos configuration and you are getting this error message:

XQE-JDB-0004 A problem occurred finding the driver class “com.ibm.db2.jcc.DB2Driver”.

This error cause because the Cognos cannot find the DB2 drivers. Solution of this problem is simple. You have to copy files db2jcc.jar and db2jcc4.jar to <Install_Cognos>\v5dataserver\lib and <Install_Cognos>\webapps\p2pd\WEB-INF\lib.

After you copy these files you need to restart the Cognos server.

DataStage: 64bit version of DataStage with 64bit Oracle Database on Windows

If you are trying to connect DataStage 64bit on Windows to Oracle Database 64bit you probably get error message like this:

DataStage was unable to attach to this connector. Error loading connector library ccora11g.dll. 
%1 is not a valid Win32 application.

1 2	DataStage was unable to attach to this connector. Error loading connector library ccora11g.dll. %1 is not a valid Win32 application.

I assume that you have done all prerequisites like set up the environment variables etc. More about prerequisites for Oracle connector in DataStage V11.3 you can find here http://ibm.co/1mu4WGo

This error message you are getting because the DataStage Engine (even in version 11.3) is still 32bit application on Windows. That means, you have to install the 32bit Oracle client and connect to Oracle DB with it. Oracle client have to be installed on the same host as DataStage Engine.

Datastage: APT_Communicator::connectTo: connect() failed due to Unix error = 10,061

If you are getting the error message while running the job:

APT_Communicator::connectTo: connect() failed due to Unix error = 10,061 (Unknown error) on node <HOSTNAME> using ConnectionInfo object 'TCP,  connection Host: HOSTNAME (<IP>), TCP port number: 0', RETRYING connect()

1	APT_Communicator::connectTo: connect() failed due to Unix error = 10,061 (Unknown error) on node <HOSTNAME> using ConnectionInfo object 'TCP, connection Host: HOSTNAME (<IP>), TCP port number: 0', RETRYING connect()

You have to follow these steps to fix the issue:

You must ensure that you have in hosts file these two entries

127.0.0.1 localhost ::1 localhost

1
2

127.0.0.1 localhost
::1 localhost
Next step is try if this commands working fine

ping -4 localhost ping -6 localhost

1
2

ping -4 localhost
ping -6 localhost
Set the parameter $APT_USE_IPV4 in DataStage project to True (1)
1. Open DataStage InfoSphere Administrator client
2. Select the project and on the properties button
3. On the general tab click on the “Environment” button
4. The parameter $APT_USE_IPV4 is located in the “Parallel” category
5. Change the value to True
6. Try run the job again!

Source: http://www-01.ibm.com/support/docview.wss?uid=swg21622965

How to convert hexadecimal number to IP address in C++

When you need to convert hexadecimal number in C++ like 0DF52286 to standard IP address format like 13.245.34.134 you can use this code:

static char* hex_to_ip(const char *input)
{
    char *output = (char*)malloc(sizeof(char) * 16);
    unsigned int a, b, c, d;

    if (sscanf(input, "%2x%2x%2x%2x", &a, &b, &c, &d) != 4)
        return output;
    sprintf(output, "%u.%u.%u.%u", a, b, c, d);
    return output;
}

static char* hex_to_ip(const char *input)

{

char *output = (char*)malloc(sizeof(char) * 16);

unsigned int a, b, c, d;

if (sscanf(input, "%2x%2x%2x%2x", &a, &b, &c, &d) != 4)

return output;

sprintf(output, "%u.%u.%u.%u", a, b, c, d);

return output;

}

The method takes one argument which is the IP address in hexadecimal format.

Datastage error: Field “NAME” has keyprep export buffer overrun error

While running a job, you getting following error:

Field "NAME" has keyprep export buffer overrun error

1	Field "NAME" has keyprep export buffer overrun error

This error happens during processing data in Lookup stage and the solution of this error is very simple. Check the key attributes in the lookup stage and ensure that all attributes have same type and length (check the extended parameter too). Continue reading →