DSXchange

I have a job that reads data from DB2, then uses the Hierarchical Data stage to compose JSON and insert those documents via a REST step into Cloudant. That's all working great! When I want to run the job a second time -- I'm going to be getting quite a few document IDs that Cloudant has already seen...

Based on the error message -- the process was encountering an issue writing to the file /tmp/XMLStage_org.apache.http.wire_0.log The whole set of /tmp/XMLStage* files were set to permissions 644 as root/system I opened a PMR with IBM, and for now I have changed the permissions on the /tmp/XMLStage* ...

I have a job to load data to Cloudant, using the Hierarchical stage -- the stage consists of a JSON Composer, REST load, and a JSON Parser. It looks to me like the REST load step is throwing an error, and maybe it's related to file permissions on the AIX server where DataStage is installed? Anyone h...

qt_ky ... now I'm embarrassed I didn't notice that earlier! Even when accessing the IIS Console via the Launch Pad, I didn't catch on that my URL containing :9080 was being changed to :9443 when I logged in. And of course, all of the links on that page are :9443. https://www-01.ibm.com/support/knowl...

qt_ky ... now I'm embarrassed I didn't notice that earlier! Even when accessing the IIS Console via the Launch Pad, I didn't catch on that my URL containing :9080 was being changed to :9443 when I logged in. And of course, all of the links on that page are :9443. https://www-01.ibm.com/support/knowl...

Same result ... unfortunately ... we accepted (most) defaults during installation, v11 still defaults to port 9080? Could not connect to server <server name here> on port [9445].<server name here>:[9445]is not reachable. Ensure that the server [<server name here>] can be resolved and that communicat...

Hi -- I'm hoping I'm just overlooking something, but I'm unable to connect my Win clients to our new v11.3.1 instance running on AIX 7.1 Here's the error message I get when attempting to connect my 11.3.1.2 Win Admin client to the AIX server. (I have masked our server name with "<server name he...

We suspect this is now a resolved issue for us ... We pursued this for nearly two months, opening a DB2/AIX PMR (77162,122,000) and also investigated our network for packet loss. Once we realized that the jobs ran well in DS v8 (on AIX 6 / DB2 9), and started noticing this issue in DS v9 (AIX 7 / DB...

We suspect this is now a resolved issue for us ... We pursued this for nearly two months, opening a DB2/AIX PMR (77162,122,000) and also investigated our network for packet loss. Once we realized that the jobs ran well in DS v8 (on AIX 6 / DB2 9), and started noticing this issue in DS v9 (AIX 7 / DB...

We're on a different version (v7 as opposed to v6) ... so the same approach may not work as well here. But, I will pass along the information that an AIX-level patch helped out with a similar scenario.

> oslevel -s
7100-02-04-1341

Do you recall which patch / OS level? We're running 7.1.0.0 right now.

That's good advice -- and we actually have DB2 & AIX Support engaged right now. All signs are pointing to something involved with the network, so our next step is to get network teams involved from the Rochester & Boulder end of things. Something is causing the ack responses from the Boulder...

I'm fairly convinced this isn't a DataStage issue, but ... the job that runs fine in v8 is having issues in v9. There's a job with a fairly complex and heavy query that runs well in v8, but is encountering a "DB2 connection closed" error in v9. The text of the error is: CLI0106E Connection...

Looks like we've solved this one -- I had a recommendation to try assigning the user who was attempting to do the metadata import to the Common Metadata Administrator role in the Web Console. My first inclination was that wasn't going to clear up a Java/.NET exception on the PC client side of things...

We have a DataStage v9.1 environment installed on AIX, and have used the metadata import functionality successfully with our DB2 sources, but have added connectivity to Netezza and are experiencing an unhandled exception error. We aren't having any trouble reading/writing data using the Netezza stag...