How freddenis/oracle-scripts works
Project type and purpose
• From the file tree and README, this is not a web or GUI application but a toolbox of Bash scripts for Oracle DB administration and monitoring (“oracle-scripts”).
• The scripts cover tasks such as ASM checks, RAC status, RMAN backups, patch listing, NFS checks, password changes, and integration with OCI.
File structure
• Top-level: a flat directory of .sh and .sql files—each script is a self-contained utility.
• Scripts are grouped by function via naming conventions:
• “gg-*.sh” → GoldenGate management
• “rac-*.sh” → Real Application Clusters status
• “exa-*.sh” → Exadata information
• “nfs-*, oci-*, rman-*, list-ohpatches.sh” → storage, cloud, backup, patching
• SQL files (.sql) contain queries the scripts invoke via SQL*Plus.
• No frontend/backend: all components run on the DBA host or bastion server.
Key components
A. DBA Host / Automation Server
• Contains all the Bash scripts (grouped by function).
• Scheduler (cron or orchestration tool) triggers them.
B. Oracle Targets
• Oracle Databases (Single instance, RAC clusters)
• ASM Instances
C. Storage / External Services
• NFS mounts
• OCI backup vault or object storage
D. Logging / Notification
• Log files, STDOUT→email or central logging (syslog / ELK etc.)
Relationships and interactions
• Scripts → Oracle via SQL*Plus or RMAN (listeners/tnsnames).
• Scripts → NFS status checks (shell commands).
• Backup scripts → OCI APIs or RMAN channels → OCI object storage.
• Output → central log or email notifications.
Architectural patterns / design principles
• Modular scripts: each does one task.
• Naming conventions group related utilities.
• Reuse of .sql queries via “pidsid.sql” or “locks.sql.”
• Clear separation of monitoring (status checks), management (start/stop), backup and reporting.