DSXchange

If the owner and user running the process do not match, it appears to be an issue. If the folder is there and owned by root or some other user other than the user running WAS, one could just recursively change the permissions throughout /tmp/informationServer. Once in the /tmp directory, all I did w...

WAS is running under the wasadmin ID. That is correct. Not sure why that folder is created with owner root. If it is deleted and you restart WAS, the folders get recreated with the owner root. Is this a bug?

I went to /tmp/informationServer directory and had noticed it was owned by root. when this structure is created, it was assigned the owner of root. I saw this yesterday and changed owner to dsadm thinking it might help. It did not. ****Resolution***** Having second thoughts today, I changed the owne...

Yes, I did stop and restart WebSphere in the steps I laid out. Since DataStage/Info Server is dependent on WAS I stopped DataStage/Info Server first doing ./uv -admin -stop. I then stopped WAS using ./stopServer.sh server1. Once WAS was stopped, I deleted the files and folders recursively in /tmp/in...

1) close Info Server Client
2) ./uv -admin -stop
3) ./stopServer.sh server1
4) cd /tmp
5) rm -R -f informationServer
6) ./startServer.sh server1
7) ./uv -admin -start
8 ) open info server client and rerun report

Unfortunately, this process did not resolve the problem.

I had this same error on v9.1 on RHEL 5.6 64 bit. I created the rest of the folders in the path and made sure the correct owner and permissions were set. I then restarted WebSphere and the initial message like you have is gone. I have a new message: ; nested exception is: com.ascential.acs.reporting...

I had the same issue and just found this. http://www-01.ibm.com/support/docview.w ... wg21459498. There appears to be a new patch.

I have not found any references to data type "XML" in any of the database connectors. I thought the SQL Server Enterprise Connector might support the XML datatype through an OLEDB connection but it echos the same error of "datatype not supported". I have tried most of the charact...

I have not found any references to data type "XML" in any of the database connectors. I thought the SQL Server Enterprise Connector might support the XML datatype through an OLEDB connection but it echos the same error of "datatype not supported". I have tried most of the charact...

I didn't get a good feel for what your scenario is. Are the key columns for your source and lookup "nullable=no" before, during, and after the lookup?

We use DataDirect for SQL Server to connect to SQL Server from our DataStage Server running on AIX. I haven't spent much time to see if there is an alternative (i.e. native SQL Server drivers for AIX?).

It works fine although traditionally, if there are native drivers they are usually faster.

I am not sure of the answer to your second question. I will have to try it.

The good thing about Find is you can do a "Find Within". This allows you to Find within your first answer set. This may get you a little bit further or offer some additional capabilities.

Instead of a "Query", maybe you could try "Find". Find is under the "Edit" menu and can be easier to use. You can find by metabroker and or class. You can also set criteria to use wildcards like *. Depending on the class you choose, only attributes for that class can be...

I think you should wait for v7 if is only a few weeks at the most. Maybe you can contiune your prototype using your current platform and change to v7 when available. I have not looked into this yet but it is my understanding there is a "web" interface between web pages you can code and Met...

I think the biggest changes in v7 were a nicer user interface and better integration with DataStage. In particular, PX support and NLS. I am not aware of any new reports per se but they have added a few new metabrokers and extended the SendToDB capabilites. Operational Metadata for DataStage 390 job...