If you need to use two copies of ORDER_PROC, why shouldn't you give the two copies the aliases ORDER_PROC_1 and ORDER_PROC_2?

If you need to use two copies of ORDER_PROC, why shouldn't you give the two copies the aliases ORDER_PROC_1 and ORDER_PROC_2?

• A. Looking in the Clarity Data Dictionary, there is a table named ORDER_PROC_2. If you were to use ORDER_PROC_2 as an alias it would be difficult to determine if you are using the ORDER_PROC_2 table or if it is an alias you have assigned to the ORDER_PROC table.
• B. Aliases must be numerically suffixed starting at 3.
• C. Using numeric aliases is prohibited.
• D. Aliases are not stored in the dataset.

Answer: (A)

The important idea is to avoid name collisions between an alias and an actual object in the data dictionary. If you alias a second copy of ORDER_PROC as ORDER_PROC_2, you run into a conflict because there is already a real object named ORDER_PROC_2 in the Clarity Data Dictionary. When a reference uses ORDER_PROC_2, the system can’t reliably tell whether you mean the actual ORDER_PROC_2 table or the alias you created for ORDER_PROC. That ambiguity can cause confusion in data mapping, queries, and integrity checks. Choosing alias names that don’t match any existing dictionary objects keeps references unambiguous. You could use a suffix that doesn’t exist, or a descriptive alias that clearly indicates it’s a copy of ORDER_PROC, avoiding collisions with real objects. The issue isn’t about prohibiting numeric aliases or where aliases are stored; it’s about preventing name clashes that blur what each reference points to.

The important idea is to avoid name collisions between an alias and an actual object in the data dictionary. If you alias a second copy of ORDER_PROC as ORDER_PROC_2, you run into a conflict because there is already a real object named ORDER_PROC_2 in the Clarity Data Dictionary. When a reference uses ORDER_PROC_2, the system can’t reliably tell whether you mean the actual ORDER_PROC_2 table or the alias you created for ORDER_PROC. That ambiguity can cause confusion in data mapping, queries, and integrity checks.

Choosing alias names that don’t match any existing dictionary objects keeps references unambiguous. You could use a suffix that doesn’t exist, or a descriptive alias that clearly indicates it’s a copy of ORDER_PROC, avoiding collisions with real objects. The issue isn’t about prohibiting numeric aliases or where aliases are stored; it’s about preventing name clashes that blur what each reference points to.