Error Message ERROR [HY000] ERROR: Base table/view ‘BLOG_LIST_TBL’ attr ‘BLOG_ID’ has changed (datatype); rebuild view ‘BLOG_LIST_VW’ What does the Error Mean? This error means that an underlying table used by the view has changed in a way, which made the view invalid, as a result, the view must be rebuilt to reflect the new table definition. How to Rebuild the view In ‘Aginity for Netezza’ this process is easy, if you have a user with sufficient permissions. The basic process is:
Tag
Showing: 1 - 10 of 11 RESULTS
Error
Infosphere – decimal_from_string Conversion Error
This is another one of those nebulas error, which can kick out of DataStage, DataQuality, and/or DataClick. This error can be particularly annoying because it doesn’t identify the field or even the precise command, which is causing the error. So, there can be more than a field and/or more than one command causing the problem. Error Conversion error calling conversion routine decimal_from_string data may have been lost Resolution To resolve this error, check for the correct formatting (date format, decimal, and null value handling) before passing to DataStage StringToDate, DateToString, DecimalToString or StringToDecimal functions. Additionally, even if the formatting is …
Netezza Connector Stage, Table name required warning for User-defined SQL Write mode
Recently, while working at a customer site and I encountered an anomaly in the Netezza Connector stage, when choosing ‘User-defined SQL’ write mode, the ‘Table name’ displays a caution/warning even though a table name should not be required. If you are using a user-defined SQL statement and/or have parametrized your SQL scripts to make the job reusable, each SQL and/or SQL script would have its own schema and table name being passed in. After some investigation, a workaround was found, which both allows you to populate table name and leverage with different schema and table names within your SQL statement and/or. Table …
Essbase Connector Error – Client Commands are Currently Not Being Accepted
While investigating a recent Infosphere Information Server (IIS), Datastage, Essbase Connect error I found the explanations of the probable causes of the error not to be terribly meaningful. So, now that I have run our error to ground, I thought it might be nice to jot down a quick note of the potential cause of the ‘Client Commands are Currently Not Being Accepted’ error, which I gleaned from the process. Error Message Id IIS-CONN-ESSBASE-01010 Error Message An error occurred while processing the request on the server. The error information is 1051544 (message on contacting or from application:[<<DateTimeStamp>>]Local////3544/Error(1013204) Client Commands are …
What are the Infosphere DataStage job status log values?
These are the job status codes seen when running Infosphere Datastage jobs and sequences. Additional information regarding a specific job or sequence error can be seen in Director. Table of dsjob utility Status Codes dsjob utility Status Codes Log/Status Description Job State Comments 0 Running Not Runnable This is the only status that means the job is actually running 1 Finished Runnable Job finished a normal run with no warnings 2 Finished (See Log) Runnable Job finished a normal run with warnings 3 Aborted Not Runnable Job finished a normal run with a fatal error 4 Queued …
Useful IIS Datastage Transformer Variables and Functions
This is a list of InfoSphere Information Server (IIS) Datastage transformer variables and functions, which I have found to be helpful over the years and tend to be frequently used. Item Description Sample INROWNUM and OUTROWNUM variables @INROWNUM and @OUTROWNUM are internal DataStage variables which do the following: ● @INROWNUM counts incoming rows to a transformer in a DataStage job ● @OUTROWNUM counts outcoming rows from a transformer in a DataStage job These variables can be used to generate sequences, primary keys, id’s, numbering rows @INROWNUM @OUTROWNUM Substring in DataStage Returns delimited substrings in a string. Syntax …
How to suppress a Change_Capture_Host warning in Datastage
Occasionally, I run into this Change Capture Host defaulting warming, so, I thought this information may be useful. Event Type Warning Message ID IIS-DSEE-TFXR-00017 Example Message Change_Capture_Host: When checking operator: Defaulting “<<FieldName>>” in transfer from “beforeRec” to “outputRec”. Setting Variable Set APT_DISABLE_TFXR0017=1 This environment variable can be added either at the project level or at the job level. Alternative Solution Within the Change Capture stage properties: Stage tab Option Property: “Change Mode Value: “Explicit key, All Values”.
DataStage – IIS-DSEE-TBLD-00008- Processing Input Record APT_Decimal Error
This another one of those nebulas error messages, which can cost a lot of time in research, if you don’t know how to simplify the process a bit. However, determining where the error is can be a bit of a challenge if you have not encountered this error before and figured out the trick, which isn’t exactly intuitive. In this case, as it turned out after I had determined where the error was, it was as simple as having missed resetting the stage variable properties, when the other decimal fields increased. How to identify where this error occurs? Disabling the …
*DataStage*DSR_SELECT (Action=3); check DataStage is set up correctly in project
Having encountered this DataStage client error in Linux a few times recently, I thought I would document the solution, which has worked for me. Error Message: Error calling subroutine: *DataStage*DSR_SELECT (Action=3); check DataStage is set up correctly in project (Subroutine failed to complete successfully (30107)) Probable Cause of Error NodeAgents has stopped running Insufficient /temp disk space Triage Approach To fix this error in Linux: Ensure disk space is available and you may want clean up the /tmp directory of any excel non-required files. Start the NodeAgents.sh, if it is not running Command to verify Node Agent is running ps …
What does “ERROR: pg_atoi: error in : can’t parse ” mean?
This is one of those vague messages, which takes a little time to run down, but once you understand it, is easily fixed. Basically, this error happens because you have mismatched and incompatible fields. Question What does “ERROR: pg_atoi: error in <ascii>: can’t parse <ascii>” mean? Answer The error is the result of an implicit conversion being performed on a character field (varchar/char) while being compared to a numeric field or value. Vendor Reference Link Implicit and explicit casting