failed to invoke GenRunTime using Phantom process helper

-
    While attempting to compile job,  “failed to invoke GenRunTime using Phantom process helper”

RC:     /tmp space might be full
           Job status is incorrect
           Format problems with projects uvodbc.config file

SOL:   a)         clean up /tmp directory
           b)        DS Director à JOB à clear status file
           c)         confirm uvodbc.config has the following entry/format:
                       [ODBC SOURCES]
                       <local uv>
                       DBMSTYPE = UNIVERSE
                       Network  = TCP/IP
                       Service =  uvserver
                       Host = 127.0.0.1

Popular posts from this blog

cognos content store database tables

-
CMSYSPROPS This table has the Content Store Version. CMOBJNAMES This table has the names of all the objects in the content store. CMOBJPROPS1 Users, Roles \ Group Distribution list and contact information such as Email, phone number, Fax Given name etc are stored in this table. CMOBJPROPS2 Report scheduling information is stored. This table has fields like hour, day week etc CMOBJPROPS3 Stores Screen Tip and Object description provided while creating the objects are stored here CMOBJPROPS4 Stores the printer paper setting details like height and width of A3 , A4 , letter and 11X17 paper orientations CMOBJPROPS6 Has the details of the all packages which were published using the FM. CMOBJPROPS7 This table stores the XML of all reports and models. This is basically to maintain the metadata about the structure of the reports and models. CMOBJPROPS10 Contact information is stored in this table. This table has columns like Contact Email and C...
Read more

How to fix: User, group, or role '*' already exists in the current database. (Microsoft SQL Server, Error: 15023)

-
Image
Create failed for User 'TMS'. (Microsoft.SqlServer.Smo) User, group, or role 'TMS' already exists in the current database. (Microsoft SQL Server, Error: 15023)   To fix this there are two different methods depending on the version of SQL Server you are using. Both of these commands re-map the user's Security Identifier (SID) to match the sql server login's SID.   SQL Server 2008 / SQL Server 2008 R2 If you have already created the server login for the user, run this in the database with the login problem. (Change ' user'  to be the database username you wish to fix, and ' serverlogin ' is the sql server login to map the user to).  ALTER USER user WITH LOGIN = serverlogin For full details of the ALTER USER command see MSDN  http://msdn.microsoft.com/en-us/library/ms176060.aspx
Read more