DSXchange

Sorry for the late response, but yes I figured out the issue. My MPP environment is currently using "Hostbased Authentication" meaning instead of RSA keys used per individual user, my servers are using SSH keys at the server/host level. Ops Console doesn't work by using "hostbased&quo...

I am attempting to uninstall Information Analyzer from Service Tier and the process get to around 25% and stalls....The process on the server side doesn't appear to be hung. The /tmp logs stop right at the point where the GUI shows "Uninstall.deploy.predefined.US.standard.rules....." Howev...

UCDI wrote:if users have been able to do this before without issue, can you re-create the dataset to see if it might just be a corrupted file?

This was correct the dataset file was corrupted. We replaced it with a good version and everything worked as it should.

Thanks!

When accessing the Dataset Management Tool after selecting the appropriate configuration file, users experience an error: Error Reading Unknown Record Schema. I have looked at all of the IBM tech notes I could find from Google and they point to a permission issue, but I have looked at the permission...

I have a v11.5.0.1 CrossMounted MPP Environment which is up and running and expected. I am attempting to configure the Operations Console to monitor the compute nodes as well. Specifically a couple of file system folders. I have configured the DSODBConfig.cfg to monitor these nodes: # Resource Track...

I am wondering if it is possible our current installed loqate installation is not compatible with RHEL v7 64bit or not compatible with AVI v10.5? Does anyone happen to know where this installation can be obtained? Or have any information on where I may be able to get a newer version of loqate?

dj wrote:In AVI Processing Path for .ini and reference files property - specify the correct AVI files path where it was installed.

Where are you suggesting I look? Are you referrring to the AVI installation directories?

Thanks,

We do have credential mapping turned on. Should the group also be added to the sssd.config? Right now, if a users is added to a specific AD group, then the sssd.config will allow them logon to the server. The error indicates not an issue though with logging on the server it looks like the roles from...

I have a new install of IIS v11.5 running on RHEL v7 using LDAP and PAM authentication. Currently I am able to add users individually via the Administration Console, then go into the Administrator client and add them specifically to a project. I attempted to add an AD Group via Administrator console...

UPDATE: After finding the previous URL's and some other threads on DSXchange....I shutdown the ASBAgent and the DS service. Then did a general ps -ef and noticed there were some lingering stale ./ASB processes from the initial install. I decided to reboot the server to clear those processes. Once th...

Some additional info. While looking through log files in the /opt/IBM/InformationServer/ASBNode/logs directory. The /asb-agent-0. out log shows this error: [06/21/16 13:16:10:946 EDT] 7233 com.ibm.iis.cas log SEVERE CDICC3401E: CC_LoadedConnector::loadLibrary, file CC_ConnectorFactory.cpp, line 1536...

Couple of questions regarding what you are asking: 1. When performing a Connectivity Test from the oracle stage inside of Designer, is this being done with the user account who is logged into Designer client or is it done by dsadm or isadmin? I ask t his because my user account logged into to the De...

thanks for the information it was most helpful. I ended up sharing out the main Engine nodes "/opt/IBM" and mounted it on the other Engine tier nodes. I tested out the compute nodes by modifying the default.apt file and jobs ran successfully.

Thanks!

I have just installed InformationServer v11.5. I have imported a job from test over to development. When I go to test the Oracle stage I get an error: "Error loading connector library libccora12c.so. libclntsh.so.12.1: cannot open shared object file: No such file or directory" I have valid...

This issue has been resolved. 99% Cause: After finishing the dev environment I exported the DB schemas and then imported them into the test environment DB. This probably caused the issue (not sure why) but is the only thing I can think of. Solution: Generated the DSODB sql scripts from the test envi...