Open up a terminal window on the server and try the following (but using whatever username/password you actually gave wacssetup ):

% mysql -u wacs -p wacs

and enter your password at the prompt. If it replies with:

ERROR 1044 (42000): Access denied for user 'wacs'@'localhost' to database 'wacs'

it is fairly safe to assume that the user account and database did not in fact get created.

Open up a terminal window on the server and try the following (but using whatever username/password you actually gave wacssetup ):

% sqlplus
SQL*Plus: Release 11.1.0.6.0 - Production on Wed Nov 18 14:58:32 2009

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Enter user-name: wacs
Enter password: 
ERROR:
ORA-01017: invalid username/password; logon denied

it is fairly safe to assume that the user account and database did not in fact get created.

Anyway, if you're seeing this kind of message, you need to verify if the database schemas did indeed get created or not. To do this, we log into SQL with the Wacs user account details as follows (change account names and passwords as appropriate):

% mysql -u wacs -p wacs
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 316
Server version: 5.0.84 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the current
 input statement.

mysql> describe conn;
+-----------+--------------+------+-----+---------+-------+
| Field     | Type         | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| centryno  | int(9)       | NO   | PRI | NULL    |       | 
| cgroup    | int(6)       | YES  |     | NULL    |       | 
| corder    | int(3)       | YES  |     | NULL    |       | 
| cflag     | char(1)      | YES  |     | NULL    |       | 
| cstatus   | char(1)      | YES  |     | NULL    |       | 
| cmodelno  | int(6)       | YES  |     | NULL    |       | 
| csetno    | int(9)       | YES  |     | NULL    |       | 
| cphotog   | varchar(6)   | YES  |     | NULL    |       | 
| ctype     | varchar(20)  | NO   |     | NULL    |       | 
| cdesc     | varchar(80)  | YES  |     | NULL    |       | 
| ccomments | varchar(240) | YES  |     | NULL    |       | 
| cpath     | varchar(160) | YES  |     | NULL    |       | 
| cadded    | date         | YES  |     | NULL    |       | 
| camended  | date         | YES  |     | NULL    |       | 
+-----------+--------------+------+-----+---------+-------+
14 rows in set (0.00 sec)

mysql> quit
%

	Note
	The SQL commands used, describe and quit are identical for Oracle although the formatting and output will differ slightly.

If you instead get a message like: ERROR 1146 (42S02): Table 'wacs.conn' doesn't exist then that is confirmation that the schema create phase had failed. Once you've resolved the cause (most likely these hostname issues), you have two choices:

If you choose to do the former option above (restart), you will need to remove the existing user account and database area as follows:

MySQL version - replace wacs and myserver.example.com as appropriate. The second drop user step may fail - that's not a problem. Be very careful indeed you have the right database name for step four!

% mysql -u root -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is xxx
Server version: 5.0.84 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> drop user 'wacs'@'localhost';
Query OK, 0 rows affected (0.01 sec)

mysql> drop user 'wacs'@'myserver';
Query OK, 0 rows affected (0.01 sec)

mysql> drop user 'wacs'@'myserver.example.com';
Query OK, 0 rows affected (0.01 sec)

mysql> drop database wacs;
Query OK, 10 rows affected (0.01 sec)

mysql> commit;
Query OK, 0 rows affected (0.00 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

mysql> quit
Bye
%

You should then be able to re-run the wacssetup web application (once of course you've worked on the root cause of the failure - most likely the IP address/DNS name issues).