If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

If you use special characters in identifiers, you need so-called "delimited identifiers". Those are described in the manual.

The major issue with such identifiers is usually not DB2 but rather your shell. For example, on UNIX systems, the shell interprets single and double quotes, interfering with the SQL statement. You can avoid this by properly escaping characters with special meaning to a shell (e.g. *, ?, ", ') or you can work with the DB2 CLP to take the shell out of the picture.

"In an SAP system there are so called name spaces for dictionary objects like database tables. The name space identifier consists of a forward slash, the name space name and another forward slash. The identifier is then part of the table name. For example the table that holds the service download customizing is called "/bdl/cust", with "bdl" being the name space."

To, I don't. Usually, I have to consider delimited identifiers because what I'm working with is rather close to the database engine and I don't know what customers are doing.

My guess on this thing is that SAP supports a wide variety of different DBMS as backend. Maybe there is even a file-based storage system possible.And because all common operating systems use '/' as directory separator, it be a way to organize things on disk without getting too big directories.