I want to find out which file is going to hold any trace information generated by my database session. Unfortunately, I keep forgetting the query that I need to run to find out.
Fortunately I’m using SQLcl, which includes the ALIAS command.
What follows is a quick run-through of this command including :
- listing the aliases that are already set up in SQLcl
- displaying the code that an alias will execute
- creating your own alias interactively
- deleting an alias
- using files to manage custom aliases
Whilst I’m at it, I’ll create the alias for the code to find that pesky trace file too.