Skip to content

Posts tagged ‘error’

Teradata database backup job failed and is not running since last failure.

ISSUE:

Teradata database backup job failed and is not running since last failure.

Job Execution Errors and Warnings:
Error Code: 1005
Error Message:
224: CLISQL Exception: CLI reported error 224: MTDP: EM_NOHOST(224): name not in HOSTS file or names database.

RESOLUTION:

You may see this issue if Teradata backup job is not able to resolve the host name in /etc/hosts. In order to fix the issue make sure the below entry in /etc/hosts file in all the COP nodes:

127.0.0.1 localhost tdatcop1 SERVERNAMEcop1

To verify this entry on all the nodes by just logging in to one node:

# psh “cat /etc/hosts | grep cop1”
all 4 nodes:
127.0.0.1 localhost tdatcop1 SERVERNAMEcop1
11.11.22.22 byn201-8 dbccop1

[Error 8017] [SQLState 28000] The UserId, Password or Account is invalid

ERROR:
Your lab group has not been created. [Teradata Database] [TeraJDBC 15.10.00.09] [Error 8017] [SQLState 28000] The UserId, Password or Account is invalid.

DESCRIPTION:
You may see above error while creating a new datalab group in viewpoint.

ISSUE:
You will see this error because the user with which you are creating data labs group do not have required permission on the underlying database where you are creating this data lab group.

RESOLUTION:
Grant below permissions to the user (sysdba in my example) and try creating the data lab group again.
GRANT USER ON DATALABS to sysdba;
GRANT CREATE ROLE to sysdba WITH GRANT OPTION;
GRANT EXECUTE ON DBC.LogonRule to sysdba;