rodrigo.pace/oracle-deep-data-security-lab
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Normalize lab docs and keep reusable TNS alias
Some checks failed
Repo Quality / structure (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Rodrigo
2026-05-18 11:30:35 -03:00
parent b8d6de0fb5
commit 2188ea8e58
17 changed files with 67 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
scenarios/02-shared-app-account/README.md
View File

@@ -19,8 +19,8 @@ Before Oracle Deep Data Security, a technical account or connection pool can que
Run SQL scripts from the repository root. On Linux/macOS/WSL:
```bash
cd ~/DEEP-DATA-SECURITY/oracle-deep-data-security-lab
export TNS_ADMIN=~/DEEP-DATA-SECURITY/wallet-ddslab
cd <repo-root>
export TNS_ADMIN=<wallet-directory>
```
Connect as the lab administrator:
@@ -31,10 +31,13 @@ sql admin@ddslab_tunnel
SQLcl note: when running a script with `@file.sql`, press Enter once and wait for the output. Do not type `/` afterward, because `/` reruns the last command in the SQLcl buffer.
Connection alias note: ddslab_tunnel is the TNS alias configured in the wallet `tnsnames.ora` for this lab. If your wallet uses another alias, replace ddslab_tunnel with your own service alias.
On Windows PowerShell:
```powershell
cd C:\Users\rodrigo\Documents\Codex\oracle-deep-data-security-lab
cd <repo-root>
sql admin@ddslab_tunnel
```