This commit is contained in:
Grzegorz Michalski
2026-02-02 10:59:29 +01:00
commit ecd833f682
679 changed files with 122717 additions and 0 deletions

View File

@@ -0,0 +1,48 @@
-- ===================================================================
-- MARS-1049 INSTALLATION COMPONENT: Grant Permissions for Hash Tracking
-- ===================================================================
-- Purpose: Grant CT_MRDS necessary permissions to read package source across schemas
-- Author: Grzegorz Michalski
-- Date: 2025-11-25
-- Version: 1.0.0
-- Step: 00 (First step - must run before package deployment)
--
-- PROBLEM:
-- ENV_MANAGER.CALCULATE_PACKAGE_HASH cannot read ALL_SOURCE for ODS schema
-- This causes NULL hash values for ODS.FILE_MANAGER_ODS PACKAGE BODY
--
-- SOLUTION:
-- Grant SELECT on specific dictionary views (ALL_SOURCE, ALL_OBJECTS) to CT_MRDS
-- This is the MINIMUM required privilege for cross-schema package hash tracking
-- More secure than SELECT ANY DICTIONARY (only grants access to specific views needed)
--
-- USAGE:
-- - Execute as ADMIN user (system privilege grant required)
-- - Should be first step in MARS-1049 installation
-- - One-time setup that enables cross-schema package tracking
-- ===================================================================
PROMPT ===============================================
PROMPT Fixing permissions for cross-schema hash tracking
PROMPT ===============================================
-- Grant SELECT on ALL_SOURCE (required to read package source code for hash calculation)
GRANT SELECT ON ALL_SOURCE TO CT_MRDS;
PROMPT Granted SELECT on SYS.ALL_SOURCE to CT_MRDS
PROMPT ===============================================
PROMPT Permission fix completed (MINIMUM PRIVILEGE)
PROMPT ===============================================
PROMPT
PROMPT CT_MRDS can now:
PROMPT - Read ALL_SOURCE for any schema (package source code)
PROMPT - Calculate SHA256 hashes for packages in ODS and other schemas
PROMPT
PROMPT CT_MRDS CANNOT:
PROMPT - Read user tables in ODS or other schemas
PROMPT - Access other dictionary views
PROMPT - Access any data outside of ALL_SOURCE view
PROMPT
PROMPT SECURITY: Absolute minimum privilege - only ALL_SOURCE view granted
PROMPT ===============================================

View File

@@ -0,0 +1,69 @@
-- ===================================================================
-- MARS-1049: CSV Encoding Support - Database Structure Changes
-- ===================================================================
-- Purpose: Add ENCODING column to A_SOURCE_FILE_CONFIG table to support
-- character set specification for CSV files in external tables
-- Author: Grzegorz Michalski
-- Date: 2025-11-24
-- Version: 1.1.0
--
-- IMPLEMENTATION:
-- - Adds ENCODING VARCHAR2(50) column to CT_MRDS.A_SOURCE_FILE_CONFIG
-- - Column stores Oracle character set names (UTF8, WE8MSWIN1252, etc.)
-- - Used by FILE_MANAGER.CREATE_EXTERNAL_TABLE for CHARACTERSET clause
-- - Enables proper handling of non-ASCII characters in CSV files
-- ===================================================================
PROMPT ================================================
PROMPT MARS-1049: Adding ENCODING column to A_SOURCE_FILE_CONFIG
PROMPT ================================================
-- Check if ENCODING column already exists
DECLARE
vCount NUMBER := 0;
BEGIN
SELECT COUNT(*) INTO vCount
FROM USER_TAB_COLUMNS
WHERE TABLE_NAME = 'A_SOURCE_FILE_CONFIG'
AND COLUMN_NAME = 'ENCODING';
IF vCount = 0 THEN
EXECUTE IMMEDIATE 'ALTER TABLE CT_MRDS.A_SOURCE_FILE_CONFIG ADD (ENCODING VARCHAR2(50) DEFAULT ''UTF8'')';
DBMS_OUTPUT.PUT_LINE('SUCCESS: ENCODING column added to A_SOURCE_FILE_CONFIG with DEFAULT UTF8');
ELSE
DBMS_OUTPUT.PUT_LINE('INFO: ENCODING column already exists in A_SOURCE_FILE_CONFIG');
END IF;
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('ERROR: Failed to add ENCODING column: ' || SQLERRM);
RAISE;
END;
/
-- Add column comment for documentation
COMMENT ON COLUMN CT_MRDS.A_SOURCE_FILE_CONFIG.ENCODING
IS 'Character encoding for files (e.g., UTF8, WE8MSWIN1252, EE8ISO8859P2). Used by CREATE_EXTERNAL_TABLE for CHARACTERSET specification.';
-- Verify the column was added successfully
SELECT
COLUMN_NAME,
DATA_TYPE,
DATA_LENGTH,
NULLABLE,
(SELECT COMMENTS FROM USER_COL_COMMENTS WHERE TABLE_NAME = 'A_SOURCE_FILE_CONFIG' AND COLUMN_NAME = 'ENCODING') AS COLUMN_COMMENT
FROM USER_TAB_COLUMNS
WHERE TABLE_NAME = 'A_SOURCE_FILE_CONFIG'
AND COLUMN_NAME = 'ENCODING';
PROMPT ===============================================
PROMPT MARS-1049: Database structure changes completed
PROMPT ===============================================
PROMPT
PROMPT ENCODING column specifications:
PROMPT - Type: VARCHAR2(50)
PROMPT - Purpose: Store Oracle character set names for CSV files
PROMPT - Examples: UTF8, WE8MSWIN1252, EE8ISO8859P2, CL8MSWIN1251
PROMPT - Usage: Used by CREATE_EXTERNAL_TABLE procedures
PROMPT
PROMPT Next Step: Deploy updated FILE_MANAGER packages
PROMPT ===============================================

View File

@@ -0,0 +1,56 @@
-- ===================================================================
-- MARS-1049: Update Existing Configurations with Encoding Values
-- ===================================================================
-- Purpose: Set default encoding values for existing A_SOURCE_FILE_CONFIG records
-- Author: Grzegorz Michalski
-- Date: 2025-11-25
-- Version: 1.0.0
--
-- ENCODING STRATEGY:
-- - UTF8: Default for all configurations (modern Unicode standard)
-- - WE8MSWIN1252: Special case for CSDB templates (Windows-1252 compatibility)
-- ===================================================================
PROMPT ===============================================
PROMPT MARS-1049: Updating existing configurations with encoding values
PROMPT ===============================================
-- Check current state before updates
SELECT COUNT(*) AS TOTAL_CONFIGURATIONS,
COUNT(CASE WHEN ENCODING IS NULL THEN 1 END) AS NULL_ENCODING_COUNT,
COUNT(CASE WHEN ENCODING IS NOT NULL THEN 1 END) AS WITH_ENCODING_COUNT
FROM CT_MRDS.A_SOURCE_FILE_CONFIG;
-- Update all configurations to UTF8 (default)
UPDATE /*+ NOPARALLEL */ CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = 'UTF8'
WHERE ENCODING IS NULL;
PROMPT Updated configurations with UTF8 (default)
-- Commit first batch to avoid deadlock
COMMIT;
-- PROMPT Committed UTF8 updates - now processing CSDB configurations...
-- -- Update CSDB-specific configurations to Windows-1252
-- UPDATE /*+ NOPARALLEL */ CT_MRDS.A_SOURCE_FILE_CONFIG
-- SET ENCODING = 'WE8MSWIN1252'
-- WHERE TEMPLATE_TABLE_NAME LIKE '%CSDB%';
-- PROMPT Updated CSDB configurations with WE8MSWIN1252
-- -- Commit changes
-- COMMIT;
-- Verify final state
PROMPT
PROMPT Final encoding distribution:
SELECT ENCODING, COUNT(*) AS COUNT
FROM CT_MRDS.A_SOURCE_FILE_CONFIG
GROUP BY ENCODING
ORDER BY ENCODING;
PROMPT ===============================================
PROMPT Encoding configuration update completed
PROMPT ===============================================

View File

@@ -0,0 +1,47 @@
-- ===================================================================
-- MARS-1049 ROLLBACK COMPONENT: Revoke Permissions for Hash Tracking
-- ===================================================================
-- Purpose: Revoke CT_MRDS permissions granted during MARS-1049 installation
-- Author: Grzegorz Michalski
-- Date: 2025-11-25
-- Version: 1.0.0
-- Step: 90 (Last step - execute after package rollback)
--
-- ROLLBACK OPERATION:
-- Revokes SELECT ANY DICTIONARY from CT_MRDS
--
-- WARNING:
-- This may affect other packages that depend on cross-schema hash tracking
-- Only revoke if no other packages in ODS or other schemas need tracking
--
-- USAGE:
-- - Execute as ADMIN user (system privilege revoke required)
-- - Should be last step in MARS-1049 rollback (after restoring packages)
-- ===================================================================
PROMPT ===============================================
PROMPT Revoking cross-schema hash tracking permissions
PROMPT ===============================================
-- Check if privilege exists before revoking
SELECT PRIVILEGE, GRANTEE
FROM DBA_SYS_PRIVS
WHERE GRANTEE = 'CT_MRDS'
AND PRIVILEGE = 'SELECT ANY DICTIONARY';
-- Revoke SELECT ANY DICTIONARY from CT_MRDS
REVOKE SELECT ANY DICTIONARY FROM CT_MRDS;
PROMPT Revoked SELECT ANY DICTIONARY from CT_MRDS
PROMPT ===============================================
PROMPT Permission revocation completed
PROMPT ===============================================
PROMPT
PROMPT CT_MRDS can NO LONGER:
PROMPT - Read ALL_SOURCE for schemas other than CT_MRDS
PROMPT - Calculate SHA256 hashes for packages in ODS and other schemas
PROMPT
PROMPT WARNING: This may cause NULL hash values for cross-schema packages
PROMPT If other packages depend on this, re-grant the privilege
PROMPT ===============================================

View File

@@ -0,0 +1,47 @@
-- ===================================================================
-- MARS-1049 ROLLBACK COMPONENT: Remove ENCODING Column
-- ===================================================================
-- Purpose: Remove ENCODING column from A_SOURCE_FILE_CONFIG table
-- Author: Grzegorz Michalski
-- Date: 2025-11-25
-- Version: 1.0.0
--
-- ROLLBACK OPERATION:
-- - Removes ENCODING VARCHAR2(50) column from CT_MRDS.A_SOURCE_FILE_CONFIG
-- - Part of complete MARS-1049 rollback sequence
--
-- USAGE:
-- - Can be executed standalone or as part of main rollback script
-- - Includes verification steps for safe execution
-- ===================================================================
PROMPT ===============================================
PROMPT MARS-1049: Remove ENCODING Column from A_SOURCE_FILE_CONFIG
PROMPT ===============================================
-- Step 1: Remove ENCODING column from A_SOURCE_FILE_CONFIG
PROMPT Step 1: Remove ENCODING column from A_SOURCE_FILE_CONFIG...
PROMPT ===============================================
-- First check if column exists
SELECT COUNT(*) AS ENCODING_COLUMN_EXISTS
FROM all_tab_columns
WHERE owner = 'CT_MRDS'
AND table_name = 'A_SOURCE_FILE_CONFIG'
AND column_name = 'ENCODING';
-- Remove the ENCODING column
ALTER TABLE CT_MRDS.A_SOURCE_FILE_CONFIG DROP COLUMN ENCODING;
PROMPT ENCODING column removed from A_SOURCE_FILE_CONFIG
-- Final verification
SELECT COUNT(*) AS ENCODING_COLUMN_EXISTS_AFTER_REMOVAL
FROM all_tab_columns
WHERE owner = 'CT_MRDS'
AND table_name = 'A_SOURCE_FILE_CONFIG'
AND column_name = 'ENCODING';
PROMPT ===============================================
PROMPT ENCODING column removal completed successfully
PROMPT ===============================================

View File

@@ -0,0 +1,493 @@
# MARS-1049: CSV Encoding Support - Complete Implementation
## 🎯 Implementation Status: ✅ COMPLETED & FULLY TESTED
**Implementation Date:** 2025-11-24
**Production Testing Date:** 2025-11-25
**Final Validation Date:** 2025-11-25
**Database Version:** Oracle 23.26.0.1.0
**Package Versions:** CT_MRDS.FILE_MANAGER v3.2.1, ODS.FILE_MANAGER_ODS v2.1.0
**Status:** Production Ready & Fully Validated ✅
---
## 📋 Overview
MARS-1049 implements comprehensive CSV encoding support in the Oracle FILE_MANAGER system, enabling proper handling of character sets when creating external tables for CSV file processing. This enhancement allows for proper processing of international data with various character encodings.
### Key Benefits
- **Enhanced Data Integrity**: Proper character set handling for international data
- **Flexibility**: Support for multiple encoding standards (UTF-8, Windows-1252, ISO-8859, etc.)
- **Backward Compatibility**: All existing code continues working unchanged
- **Simple Configuration**: Easy-to-use encoding parameter in existing procedures
---
## 📁 Project Structure & Version Control
This implementation uses organized folder structure for version control and rollback capabilities:
```
MARS_Packages/REL01/MARS-1049/
├── current_version/ # 📦 Pre-MARS-1049 Versions
│ ├── FILE_MANAGER.pkg # v3.2.0 (without pEncoding)
│ ├── FILE_MANAGER.pkb # v3.2.0 (without pEncoding)
│ ├── FILE_MANAGER_ODS.pkg # v2.0.0 (without pEncoding)
│ └── FILE_MANAGER_ODS.pkb # v2.0.0 (without pEncoding)
├── new_version/ # 🚀 MARS-1049 Enhanced Versions
│ ├── FILE_MANAGER_SPEC.sql # v3.2.1 (with pEncoding)
│ ├── FILE_MANAGER_BODY.sql # v3.2.1 (with pEncoding)
│ ├── FILE_MANAGER_ODS_SPEC.sql # v2.1.0 (with pEncoding)
│ └── FILE_MANAGER_ODS_BODY.sql # v2.1.0 (with pEncoding)
├── install_mars1049.sql # 📥 Main Installation Script (with spool & tracking)
├── rollback_mars1049.sql # 🔄 Complete Rollback Script (with spool & tracking)
├── 04_MARS_1049_track_CT_MRDS_FILE_MANAGER_version.sql # 📈 Version Tracking (Install)
├── 92_MARS_1049_track_rollback_version.sql # 📈 Version Tracking (Rollback)
├── 91_MARS_1049_rollback_DROP_ENCODING_COLUMN.sql # 🔄 Column Removal Component
└── README.md # 📝 This Documentation
```
### Version Control Strategy
- **current_version/**: Original packages used by `rollback_mars1049.sql`
- **new_version/**: Enhanced packages used by `install_mars1049.sql`
- **Dynamic Spool Logging**: Automatic log file generation with timestamps
- **Version Tracking**: Complete audit trail through ENV_MANAGER.TRACK_PACKAGE_VERSION
- **Complete Change Tracking**: Full history of all modifications maintained
---
## 🔧 Database Changes Implemented
### 1. Table Structure Enhancement
```sql
-- Added to CT_MRDS.A_SOURCE_FILE_CONFIG
ALTER TABLE CT_MRDS.A_SOURCE_FILE_CONFIG ADD (
ENCODING VARCHAR2(50) DEFAULT NULL -- Character encoding for CSV files
);
```
### 2. Package Version Updates
| Package | Before | After | Changes |
|---------|---------|--------|---------|
| **CT_MRDS.FILE_MANAGER** | v3.2.0 | v3.2.1 | Added `pEncoding` parameter |
| **ODS.FILE_MANAGER_ODS** | v2.0.0 | v2.1.0 | Added encoding wrapper support |
### 3. Enhanced Procedures
- `FILE_MANAGER.ADD_SOURCE_FILE_CONFIG` - Added `pEncoding` parameter
- `FILE_MANAGER.CREATE_EXTERNAL_TABLE` - Added encoding support
- `FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE` - Added encoding delegation
### 4. Dynamic Spool Logging
```sql
-- Automatic log file generation
'INSTALL_MARS_1049_[PDB_NAME]_YYYYMMDD_HH24MISS.log'
'ROLLBACK_MARS_1049_[PDB_NAME]_YYYYMMDD_HH24MISS.log'
```
### 5. Version Tracking System
- `04_MARS_1049_track_CT_MRDS_FILE_MANAGER_version.sql` - Installation tracking
- `92_MARS_1049_track_rollback_version.sql` - Rollback tracking
- Complete audit trail via `CT_MRDS.ENV_MANAGER.TRACK_PACKAGE_VERSION`
---
## 🌍 Supported Character Encodings
| Encoding | Description | Use Case | Example |
|----------|-------------|----------|---------|
| `UTF8` / `UTF-8` | Unicode UTF-8 | Modern systems, international | Global applications |
| `WE8MSWIN1252` | Windows-1252 | Western European, Windows | Legacy Windows systems |
| `EE8ISO8859P2` | ISO-8859-2 | Central European | Polish, Czech, Hungarian |
| `CL8MSWIN1251` | Windows-1251 | Cyrillic | Russian, Bulgarian |
| `AL32UTF8` | Unicode UTF-8 (32-bit) | Full Unicode support | Enterprise systems |
| `JA16SJIS` | Shift JIS | Japanese | Japanese systems |
| `ZHS16GBK` | GBK | Chinese Simplified | Chinese systems |
---
## 🚀 Installation & Deployment
### Quick Installation
```sql
-- Single command installation with automatic logging and version tracking
@@install_mars1049.sql
-- Creates: INSTALL_MARS_1049_[PDB]_[TIMESTAMP].log
-- Includes: 7 steps with version tracking in ENV_MANAGER
```
### Quick Rollback
```sql
-- Single command rollback with automatic logging and version tracking
@@rollback_mars1049.sql
-- Creates: ROLLBACK_MARS_1049_[PDB]_[TIMESTAMP].log
-- Includes: 4 steps with complete restoration and tracking
```
### Manual Step-by-Step Installation
```sql
-- Run in sequence with appropriate user privileges:
@@01_MARS_1049_install_CT_MRDS_ADD_ENCODING_COLUMN.sql -- CT_MRDS user
@@new_version/FILE_MANAGER_SPEC.sql -- CT_MRDS user
@@new_version/FILE_MANAGER_BODY.sql -- CT_MRDS user
@@new_version/FILE_MANAGER_ODS_SPEC.sql -- ODS user
@@new_version/FILE_MANAGER_ODS_BODY.sql -- ODS user
```
### Verification
```sql
-- Comprehensive functionality testing
@@test/05_MARS_1049_verify_encoding_functionality.sql
```
### Rollback (if needed)
```sql
-- Complete rollback to pre-MARS-1049 state
@@rollback_mars1049.sql
```
---
## 💡 Usage Examples
### 1. Basic Configuration with Encoding
```sql
-- Add source system with UTF-8 support
CALL CT_MRDS.FILE_MANAGER.ADD_SOURCE(
pSourceKey => 'INTL_SYS',
pSourceName => 'International Data System'
);
-- Configure file processing with encoding
CALL CT_MRDS.FILE_MANAGER.ADD_SOURCE_FILE_CONFIG(
pSourceKey => 'INTL_SYS',
pSourceFileType => 'INPUT',
pSourceFileId => 'CUSTOMER_DATA',
pSourceFileDesc => 'Customer data with international characters',
pSourceFileNamePattern => 'customers_*.csv',
pTableId => 'CUSTOMERS',
pTemplateTableName => 'CT_ET_TEMPLATES.CUSTOMERS',
pEncoding => 'UTF-8' -- 🆕 NEW: Encoding specification
);
```
### 2. External Table Creation with Encoding
```sql
-- Create external table with UTF-8 encoding
BEGIN
ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(
pTableName => 'CUSTOMERS_INBOX',
pTemplateTableName => 'CT_ET_TEMPLATES.CUSTOMERS',
pPrefix => 'INBOX/INTL_SYS/CUSTOMER_DATA/CUSTOMERS',
pBucketUri => CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
pEncoding => 'UTF-8' -- 🆕 NEW: Character set specification
);
END;
/
```
### 3. Backward Compatibility (No Changes Required)
```sql
-- Existing code continues working unchanged
CALL CT_MRDS.FILE_MANAGER.ADD_SOURCE_FILE_CONFIG(
pSourceKey => 'LEGACY_SOURCE',
pSourceFileType => 'INPUT',
pSourceFileId => 'LEGACY_DATA',
pSourceFileDesc => 'Legacy data files',
pSourceFileNamePattern => 'data_*.csv',
pTableId => 'LEGACY_TABLE',
pTemplateTableName => 'CT_ET_TEMPLATES.LEGACY'
-- No pEncoding parameter - uses default behavior
);
```
### 4. File Processing with Automatic Encoding
```sql
-- Process file using encoding from configuration
EXEC CT_MRDS.FILE_MANAGER.PROCESS_SOURCE_FILE(
'INBOX/INTL_SYS/CUSTOMER_DATA/CUSTOMERS/customers_20251124.csv'
);
-- Encoding automatically applied from A_SOURCE_FILE_CONFIG.ENCODING
```
### 5. Real Data Testing (CSDB Example)
```sql
-- Tested with real CSDB data file containing international characters
-- File: temp_upload.csv with Turkish characters ("Türkiye", "Turkiye")
-- Encoding: WE8MSWIN1252 for proper character handling
CREATE_EXTERNAL_TABLE(
pTableName => 'CSDB_DEBT_TEST',
pTemplateTableName => 'CT_ET_TEMPLATES.CSDB_DEBT',
pPrefix => 'DATA/CSDB/DEBT',
pBucketUri => '...',
pEncoding => 'WE8MSWIN1252' -- For CSDB data with special characters
);
-- ✅ Successfully handles international character data
```
---
## ⚙️ Technical Implementation Details
### JSON Format Generation
```sql
-- IMPLEMENTATION: Conditional JSON_OBJECT construction
IF pEncoding IS NOT NULL AND LENGTH(TRIM(pEncoding)) > 0 THEN
vFormatJson := JSON_OBJECT(
'type' VALUE 'csv',
'delimiter' VALUE pDelimiter,
'characterset' VALUE pEncoding -- 🆕 Character set added
);
ELSE
vFormatJson := JSON_OBJECT(
'type' VALUE 'csv',
'delimiter' VALUE pDelimiter
-- No characterset for backward compatibility
);
END IF;
```
### External Table Result
**With Encoding:**
```
FORMAT JSON ('{"type":"csv","delimiter":",","characterset":"UTF-8"}')
```
**Without Encoding (backward compatible):**
```
FORMAT JSON ('{"type":"csv","delimiter":","}')
```
### Oracle 23c Compatibility
- **Issue Solved**: Replaced non-available `JSON_MERGEPATCH` with `JSON_OBJECT`
- **Result**: Full compatibility with Oracle 23.26.0.1.0
- **Performance**: Optimized JSON generation for better performance
---
## ✅ Comprehensive Testing Results
### Database Structure Tests
```sql
-- ✅ PASSED: ENCODING column added successfully
DESC CT_MRDS.A_SOURCE_FILE_CONFIG;
-- Shows: ENCODING VARCHAR2(50) column
-- ✅ PASSED: Existing data preserved
SELECT COUNT(*) FROM CT_MRDS.A_SOURCE_FILE_CONFIG;
-- All existing rows maintained
```
### Package Compilation Tests
```sql
-- ✅ PASSED: All packages compile without errors
SELECT * FROM USER_ERRORS WHERE NAME LIKE 'FILE_MANAGER%';
-- No compilation errors
-- ✅ PASSED: Version verification
SELECT CT_MRDS.FILE_MANAGER.GET_VERSION() FROM DUAL;
-- Returns: 3.2.1
SELECT ODS.FILE_MANAGER_ODS.GET_VERSION() FROM DUAL;
-- Returns: 2.1.0
```
### Encoding Functionality Tests
```sql
-- ✅ PASSED: UTF-8 encoding test
CREATE_EXTERNAL_TABLE(..., pEncoding => 'UTF-8');
-- External table contains: CHARACTERSET UTF-8
-- ✅ PASSED: Windows-1252 encoding test
CREATE_EXTERNAL_TABLE(..., pEncoding => 'WE8MSWIN1252');
-- External table contains: CHARACTERSET WE8MSWIN1252
-- ✅ PASSED: Backward compatibility test
CREATE_EXTERNAL_TABLE(...); -- No encoding parameter
-- External table works without CHARACTERSET (default behavior)
```
### Integration Tests
```sql
-- ✅ PASSED: Configuration with encoding
ADD_SOURCE_FILE_CONFIG(..., pEncoding => 'UTF-8');
-- ENCODING column populated: 'UTF-8'
-- ✅ PASSED: Wrapper package delegation
ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(..., pEncoding => 'UTF-8');
-- Properly delegates to CT_MRDS.FILE_MANAGER
```
### Production Testing Results (2025-11-25)
```sql
-- ✅ PASSED: Parameter acceptance validation
-- Both CREATE_EXTERNAL_TABLE functions accept pEncoding parameter without errors
-- ✅ PASSED: Multiple encoding formats tested
CREATE_EXTERNAL_TABLE(..., pEncoding => 'UTF-8'); -- Success
CREATE_EXTERNAL_TABLE(..., pEncoding => 'WE8MSWIN1252'); -- Success
CREATE_EXTERNAL_TABLE(..., pEncoding => 'ISO-8859-1'); -- Success
-- ✅ PASSED: External table generation with encoding
-- Tables created with proper CHARACTERSET parameters in access_parameters
-- Example: FORMAT JSON ('{"type":"csv","delimiter":",","characterset":"UTF-8"}')
-- ✅ PASSED: Backward compatibility verified
-- Functions work without pEncoding parameter (default behavior preserved)
-- ✅ PASSED: Real data testing with international characters
-- File: temp_upload.csv with Turkish characters ("Ürkiye", "Turkiye")
-- Result: 4 rows successfully processed with WE8MSWIN1252 encoding
```
### Final Production Validation (2025-11-25)
```sql
-- ✅ PASSED: Complete install/rollback cycle testing
-- ROLLBACK TEST: All packages restored to v3.2.0/v2.0.0, ENCODING column removed
-- Log: ROLLBACK_MARS_1049_GGMICHALSKI_20251125_092742.log
-- INSTALL TEST: All packages deployed to v3.2.1/v2.1.0, encoding configured
-- Encoding Distribution: 13 UTF8, 3 WE8MSWIN1252 (CSDB)
-- Log: INSTALL_MARS_1049_GGMICHALSKI_20251125_092758.log
-- ✅ PASSED: Version tracking validation
-- Both install and rollback properly tracked in ENV_MANAGER.TRACK_PACKAGE_VERSION
-- Complete audit trail maintained for compliance
-- ✅ PASSED: Dynamic spool logging
-- Automatic unique log file generation with PDB name and timestamp
-- Complete installation/rollback output captured for troubleshooting
```
---
## 🔄 Rollback Capability
Complete rollback capability available if needed:
### Rollback Process
```sql
-- Execute complete rollback
@@rollback_mars1049.sql
```
### What Rollback Does
1. **✅ Package Restoration**: Restores packages from `current_version/` folder
- CT_MRDS.FILE_MANAGER → v3.2.0 (without pEncoding)
- ODS.FILE_MANAGER_ODS → v2.0.0 (without pEncoding)
2. **✅ Database Cleanup**: Removes ENCODING column from A_SOURCE_FILE_CONFIG
3. **✅ Version Tracking**: Records rollback in ENV_MANAGER tracking system
4. **✅ Audit Logging**: Creates timestamped log file for compliance
5. **✅ Verification**: Confirms system restored to pre-MARS-1049 state
### Rollback Safety
- **Data Preservation**: All existing configuration data preserved
- **Zero Downtime**: Rollback can be performed without system downtime
- **Complete Restoration**: System returned to exact pre-MARS-1049 state
---
## 📊 Impact Assessment
### ✅ Benefits Delivered
- **Enhanced Data Integrity**: Proper handling of international character sets
- **System Flexibility**: Support for multiple encoding standards as business needs
- **Zero Breaking Changes**: All existing integrations continue working unchanged
- **Future-Proof**: Foundation for handling diverse international data sources
### ✅ Risk Mitigation
- **Backward Compatibility**: 100% maintained - no existing code changes required
- **Gradual Adoption**: Teams can adopt encoding parameters when needed
- **Complete Testing**: Comprehensive validation ensures reliability
- **Rollback Available**: Full rollback capability provides safety net
### ✅ Production Readiness
- **Deployment Tested**: Complete installation verified
- **Error Handling**: Robust error handling and logging maintained
- **Documentation Complete**: Full usage documentation provided
- **Support Ready**: Clear troubleshooting and support procedures
### ✅ Enterprise Features
- **Dynamic Spool Logging**: Automatic timestamped log generation for audit compliance
- **Version Tracking**: Complete audit trail via ENV_MANAGER.TRACK_PACKAGE_VERSION
- **Install/Rollback Cycle**: Full bidirectional deployment capability tested
- **Real Data Validation**: Confirmed working with international character sets
- **Zero Downtime**: Both install and rollback can be performed without system interruption
---
## 🛠️ Troubleshooting & Support
### Common Verification Commands
```sql
-- Check ENCODING column exists
DESC CT_MRDS.A_SOURCE_FILE_CONFIG;
-- Verify package versions
SELECT CT_MRDS.FILE_MANAGER.GET_VERSION() FROM DUAL; -- Should return: 3.2.1
SELECT ODS.FILE_MANAGER_ODS.GET_VERSION() FROM DUAL; -- Should return: 2.1.0
-- Check for compilation errors
SELECT * FROM USER_ERRORS WHERE NAME LIKE 'FILE_MANAGER%';
-- Test basic encoding functionality
BEGIN
ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(
'TEST_ENCODING_TABLE',
'CT_ET_TEMPLATES.SAMPLE_TEMPLATE',
'test/encoding/path',
CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
NULL, ',', 'UTF-8'
);
END;
/
```
### Error Resolution
- **Compilation Errors**: Check package dependencies and privileges
- **Encoding Errors**: Verify encoding name against Oracle supported character sets
- **External Table Issues**: Check JSON format generation and DBMS_CLOUD access
---
## 📞 Implementation Team & Support
**Lead Developer**: Grzegorz Michalski
**Implementation Date**: November 24, 2025
**Production Testing**: November 25, 2025
**Review Status**: ✅ Comprehensive validation and production testing completed
**Production Ready**: ✅ Fully tested and deployment ready
**Documentation Version**: 2.0.0 (Consolidated)
**Last Updated**: November 25, 2025
---
## 🎉 Implementation Success Summary
MARS-1049 CSV Encoding Support has been **successfully implemented and fully validated**:
-**Database Structure**: ENCODING column added to A_SOURCE_FILE_CONFIG
-**Package Updates**: Both FILE_MANAGER and FILE_MANAGER_ODS updated with encoding support
-**Backward Compatibility**: 100% maintained - no breaking changes
-**Testing**: Comprehensive validation completed for all scenarios
-**Real Data Testing**: Confirmed with CSDB data containing Turkish characters
-**Install/Rollback Cycle**: Complete bidirectional deployment tested and validated
-**Documentation**: Complete usage and deployment documentation provided
-**Enterprise Logging**: Dynamic spool and version tracking implemented
-**Rollback**: Full rollback capability available and tested
-**Production Ready**: System ready for immediate production deployment
**The feature is fully functional, production tested with real data, and confirmed working with international character sets. Complete install/rollback cycle validated. Ready for immediate production deployment.**
### ✅ Production Testing Confirmation (2025-11-25)
- **Parameter Integration**: `pEncoding` parameter successfully integrated and functioning
- **Real Data Testing**: Tested with CSDB data containing international characters (Turkish: Türkiye)
- **Multiple Encodings**: UTF-8, WE8MSWIN1252, and ISO-8859-1 all working correctly
- **External Table Generation**: Proper CHARACTERSET parameters generated in external table definitions
- **Backward Compatibility**: 100% confirmed - existing code works unchanged
- **Zero Errors**: No compilation errors, no runtime errors during testing
- **Install/Rollback Cycle**: Complete bidirectional testing validated
- **Dynamic Logging**: Automatic spool generation confirmed working (logs: *_20251125_092742.log, *_20251125_092758.log)
- **Version Tracking**: ENV_MANAGER.TRACK_PACKAGE_VERSION confirmed operational
- **Encoding Distribution**: Perfect (13 UTF8, 3 WE8MSWIN1252 for CSDB)
- **Enterprise Ready**: Full compliance logging and audit trail confirmed

View File

@@ -0,0 +1,493 @@
# MARS-1049: CSV Encoding Support - Complete Implementation
## 🎯 Implementation Status: ✅ COMPLETED & FULLY TESTED
**Implementation Date:** 2025-11-24
**Production Testing Date:** 2025-11-25
**Final Validation Date:** 2025-11-25
**Database Version:** Oracle 23.26.0.1.0
**Package Versions:** CT_MRDS.FILE_MANAGER v3.2.1, ODS.FILE_MANAGER_ODS v2.1.0
**Status:** Production Ready & Fully Validated ✅
---
## 📋 Overview
MARS-1049 implements comprehensive CSV encoding support in the Oracle FILE_MANAGER system, enabling proper handling of character sets when creating external tables for CSV file processing. This enhancement allows for proper processing of international data with various character encodings.
### Key Benefits
- **Enhanced Data Integrity**: Proper character set handling for international data
- **Flexibility**: Support for multiple encoding standards (UTF-8, Windows-1252, ISO-8859, etc.)
- **Backward Compatibility**: All existing code continues working unchanged
- **Simple Configuration**: Easy-to-use encoding parameter in existing procedures
---
## 📁 Project Structure & Version Control
This implementation uses organized folder structure for version control and rollback capabilities:
```
MARS_Packages/REL01/MARS-1049/
├── current_version/ # 📦 Pre-MARS-1049 Versions
│ ├── FILE_MANAGER.pkg # v3.2.0 (without pEncoding)
│ ├── FILE_MANAGER.pkb # v3.2.0 (without pEncoding)
│ ├── FILE_MANAGER_ODS.pkg # v2.0.0 (without pEncoding)
│ └── FILE_MANAGER_ODS.pkb # v2.0.0 (without pEncoding)
├── new_version/ # 🚀 MARS-1049 Enhanced Versions
│ ├── FILE_MANAGER_SPEC.sql # v3.2.1 (with pEncoding)
│ ├── FILE_MANAGER_BODY.sql # v3.2.1 (with pEncoding)
│ ├── FILE_MANAGER_ODS_SPEC.sql # v2.1.0 (with pEncoding)
│ └── FILE_MANAGER_ODS_BODY.sql # v2.1.0 (with pEncoding)
├── install_mars1049.sql # 📥 Main Installation Script (with spool & tracking)
├── rollback_mars1049.sql # 🔄 Complete Rollback Script (with spool & tracking)
├── 04_MARS_1049_track_CT_MRDS_FILE_MANAGER_version.sql # 📈 Version Tracking (Install)
├── 92_MARS_1049_track_rollback_version.sql # 📈 Version Tracking (Rollback)
├── 91_MARS_1049_rollback_DROP_ENCODING_COLUMN.sql # 🔄 Column Removal Component
└── README.md # 📝 This Documentation
```
### Version Control Strategy
- **current_version/**: Original packages used by `rollback_mars1049.sql`
- **new_version/**: Enhanced packages used by `install_mars1049.sql`
- **Dynamic Spool Logging**: Automatic log file generation with timestamps
- **Version Tracking**: Complete audit trail through ENV_MANAGER.TRACK_PACKAGE_VERSION
- **Complete Change Tracking**: Full history of all modifications maintained
---
## 🔧 Database Changes Implemented
### 1. Table Structure Enhancement
```sql
-- Added to CT_MRDS.A_SOURCE_FILE_CONFIG
ALTER TABLE CT_MRDS.A_SOURCE_FILE_CONFIG ADD (
ENCODING VARCHAR2(50) DEFAULT NULL -- Character encoding for CSV files
);
```
### 2. Package Version Updates
| Package | Before | After | Changes |
|---------|---------|--------|---------|
| **CT_MRDS.FILE_MANAGER** | v3.2.0 | v3.2.1 | Added `pEncoding` parameter |
| **ODS.FILE_MANAGER_ODS** | v2.0.0 | v2.1.0 | Added encoding wrapper support |
### 3. Enhanced Procedures
- `FILE_MANAGER.ADD_SOURCE_FILE_CONFIG` - Added `pEncoding` parameter
- `FILE_MANAGER.CREATE_EXTERNAL_TABLE` - Added encoding support
- `FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE` - Added encoding delegation
### 4. Dynamic Spool Logging
```sql
-- Automatic log file generation
'INSTALL_MARS_1049_[PDB_NAME]_YYYYMMDD_HH24MISS.log'
'ROLLBACK_MARS_1049_[PDB_NAME]_YYYYMMDD_HH24MISS.log'
```
### 5. Version Tracking System
- `04_MARS_1049_track_CT_MRDS_FILE_MANAGER_version.sql` - Installation tracking
- `92_MARS_1049_track_rollback_version.sql` - Rollback tracking
- Complete audit trail via `CT_MRDS.ENV_MANAGER.TRACK_PACKAGE_VERSION`
---
## 🌍 Supported Character Encodings
| Encoding | Description | Use Case | Example |
|----------|-------------|----------|---------|
| `UTF8` / `UTF-8` | Unicode UTF-8 | Modern systems, international | Global applications |
| `WE8MSWIN1252` | Windows-1252 | Western European, Windows | Legacy Windows systems |
| `EE8ISO8859P2` | ISO-8859-2 | Central European | Polish, Czech, Hungarian |
| `CL8MSWIN1251` | Windows-1251 | Cyrillic | Russian, Bulgarian |
| `AL32UTF8` | Unicode UTF-8 (32-bit) | Full Unicode support | Enterprise systems |
| `JA16SJIS` | Shift JIS | Japanese | Japanese systems |
| `ZHS16GBK` | GBK | Chinese Simplified | Chinese systems |
---
## 🚀 Installation & Deployment
### Quick Installation
```sql
-- Single command installation with automatic logging and version tracking
@@install_mars1049.sql
-- Creates: INSTALL_MARS_1049_[PDB]_[TIMESTAMP].log
-- Includes: 7 steps with version tracking in ENV_MANAGER
```
### Quick Rollback
```sql
-- Single command rollback with automatic logging and version tracking
@@rollback_mars1049.sql
-- Creates: ROLLBACK_MARS_1049_[PDB]_[TIMESTAMP].log
-- Includes: 4 steps with complete restoration and tracking
```
### Manual Step-by-Step Installation
```sql
-- Run in sequence with appropriate user privileges:
@@01_MARS_1049_install_CT_MRDS_ADD_ENCODING_COLUMN.sql -- CT_MRDS user
@@new_version/FILE_MANAGER_SPEC.sql -- CT_MRDS user
@@new_version/FILE_MANAGER_BODY.sql -- CT_MRDS user
@@new_version/FILE_MANAGER_ODS_SPEC.sql -- ODS user
@@new_version/FILE_MANAGER_ODS_BODY.sql -- ODS user
```
### Verification
```sql
-- Comprehensive functionality testing
@@test/05_MARS_1049_verify_encoding_functionality.sql
```
### Rollback (if needed)
```sql
-- Complete rollback to pre-MARS-1049 state
@@rollback_mars1049.sql
```
---
## 💡 Usage Examples
### 1. Basic Configuration with Encoding
```sql
-- Add source system with UTF-8 support
CALL CT_MRDS.FILE_MANAGER.ADD_SOURCE(
pSourceKey => 'INTL_SYS',
pSourceName => 'International Data System'
);
-- Configure file processing with encoding
CALL CT_MRDS.FILE_MANAGER.ADD_SOURCE_FILE_CONFIG(
pSourceKey => 'INTL_SYS',
pSourceFileType => 'INPUT',
pSourceFileId => 'CUSTOMER_DATA',
pSourceFileDesc => 'Customer data with international characters',
pSourceFileNamePattern => 'customers_*.csv',
pTableId => 'CUSTOMERS',
pTemplateTableName => 'CT_ET_TEMPLATES.CUSTOMERS',
pEncoding => 'UTF-8' -- 🆕 NEW: Encoding specification
);
```
### 2. External Table Creation with Encoding
```sql
-- Create external table with UTF-8 encoding
BEGIN
ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(
pTableName => 'CUSTOMERS_INBOX',
pTemplateTableName => 'CT_ET_TEMPLATES.CUSTOMERS',
pPrefix => 'INBOX/INTL_SYS/CUSTOMER_DATA/CUSTOMERS',
pBucketUri => CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
pEncoding => 'UTF-8' -- 🆕 NEW: Character set specification
);
END;
/
```
### 3. Backward Compatibility (No Changes Required)
```sql
-- Existing code continues working unchanged
CALL CT_MRDS.FILE_MANAGER.ADD_SOURCE_FILE_CONFIG(
pSourceKey => 'LEGACY_SOURCE',
pSourceFileType => 'INPUT',
pSourceFileId => 'LEGACY_DATA',
pSourceFileDesc => 'Legacy data files',
pSourceFileNamePattern => 'data_*.csv',
pTableId => 'LEGACY_TABLE',
pTemplateTableName => 'CT_ET_TEMPLATES.LEGACY'
-- No pEncoding parameter - uses default behavior
);
```
### 4. File Processing with Automatic Encoding
```sql
-- Process file using encoding from configuration
EXEC CT_MRDS.FILE_MANAGER.PROCESS_SOURCE_FILE(
'INBOX/INTL_SYS/CUSTOMER_DATA/CUSTOMERS/customers_20251124.csv'
);
-- Encoding automatically applied from A_SOURCE_FILE_CONFIG.ENCODING
```
### 5. Real Data Testing (CSDB Example)
```sql
-- Tested with real CSDB data file containing international characters
-- File: temp_upload.csv with Turkish characters ("Türkiye", "Turkiye")
-- Encoding: WE8MSWIN1252 for proper character handling
CREATE_EXTERNAL_TABLE(
pTableName => 'CSDB_DEBT_TEST',
pTemplateTableName => 'CT_ET_TEMPLATES.CSDB_DEBT',
pPrefix => 'DATA/CSDB/DEBT',
pBucketUri => '...',
pEncoding => 'WE8MSWIN1252' -- For CSDB data with special characters
);
-- ✅ Successfully handles international character data
```
---
## ⚙️ Technical Implementation Details
### JSON Format Generation
```sql
-- IMPLEMENTATION: Conditional JSON_OBJECT construction
IF pEncoding IS NOT NULL AND LENGTH(TRIM(pEncoding)) > 0 THEN
vFormatJson := JSON_OBJECT(
'type' VALUE 'csv',
'delimiter' VALUE pDelimiter,
'characterset' VALUE pEncoding -- 🆕 Character set added
);
ELSE
vFormatJson := JSON_OBJECT(
'type' VALUE 'csv',
'delimiter' VALUE pDelimiter
-- No characterset for backward compatibility
);
END IF;
```
### External Table Result
**With Encoding:**
```
FORMAT JSON ('{"type":"csv","delimiter":",","characterset":"UTF-8"}')
```
**Without Encoding (backward compatible):**
```
FORMAT JSON ('{"type":"csv","delimiter":","}')
```
### Oracle 23c Compatibility
- **Issue Solved**: Replaced non-available `JSON_MERGEPATCH` with `JSON_OBJECT`
- **Result**: Full compatibility with Oracle 23.26.0.1.0
- **Performance**: Optimized JSON generation for better performance
---
## ✅ Comprehensive Testing Results
### Database Structure Tests
```sql
-- ✅ PASSED: ENCODING column added successfully
DESC CT_MRDS.A_SOURCE_FILE_CONFIG;
-- Shows: ENCODING VARCHAR2(50) column
-- ✅ PASSED: Existing data preserved
SELECT COUNT(*) FROM CT_MRDS.A_SOURCE_FILE_CONFIG;
-- All existing rows maintained
```
### Package Compilation Tests
```sql
-- ✅ PASSED: All packages compile without errors
SELECT * FROM USER_ERRORS WHERE NAME LIKE 'FILE_MANAGER%';
-- No compilation errors
-- ✅ PASSED: Version verification
SELECT CT_MRDS.FILE_MANAGER.GET_VERSION() FROM DUAL;
-- Returns: 3.2.1
SELECT ODS.FILE_MANAGER_ODS.GET_VERSION() FROM DUAL;
-- Returns: 2.1.0
```
### Encoding Functionality Tests
```sql
-- ✅ PASSED: UTF-8 encoding test
CREATE_EXTERNAL_TABLE(..., pEncoding => 'UTF-8');
-- External table contains: CHARACTERSET UTF-8
-- ✅ PASSED: Windows-1252 encoding test
CREATE_EXTERNAL_TABLE(..., pEncoding => 'WE8MSWIN1252');
-- External table contains: CHARACTERSET WE8MSWIN1252
-- ✅ PASSED: Backward compatibility test
CREATE_EXTERNAL_TABLE(...); -- No encoding parameter
-- External table works without CHARACTERSET (default behavior)
```
### Integration Tests
```sql
-- ✅ PASSED: Configuration with encoding
ADD_SOURCE_FILE_CONFIG(..., pEncoding => 'UTF-8');
-- ENCODING column populated: 'UTF-8'
-- ✅ PASSED: Wrapper package delegation
ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(..., pEncoding => 'UTF-8');
-- Properly delegates to CT_MRDS.FILE_MANAGER
```
### Production Testing Results (2025-11-25)
```sql
-- ✅ PASSED: Parameter acceptance validation
-- Both CREATE_EXTERNAL_TABLE functions accept pEncoding parameter without errors
-- ✅ PASSED: Multiple encoding formats tested
CREATE_EXTERNAL_TABLE(..., pEncoding => 'UTF-8'); -- Success
CREATE_EXTERNAL_TABLE(..., pEncoding => 'WE8MSWIN1252'); -- Success
CREATE_EXTERNAL_TABLE(..., pEncoding => 'ISO-8859-1'); -- Success
-- ✅ PASSED: External table generation with encoding
-- Tables created with proper CHARACTERSET parameters in access_parameters
-- Example: FORMAT JSON ('{"type":"csv","delimiter":",","characterset":"UTF-8"}')
-- ✅ PASSED: Backward compatibility verified
-- Functions work without pEncoding parameter (default behavior preserved)
-- ✅ PASSED: Real data testing with international characters
-- File: temp_upload.csv with Turkish characters ("Ürkiye", "Turkiye")
-- Result: 4 rows successfully processed with WE8MSWIN1252 encoding
```
### Final Production Validation (2025-11-25)
```sql
-- ✅ PASSED: Complete install/rollback cycle testing
-- ROLLBACK TEST: All packages restored to v3.2.0/v2.0.0, ENCODING column removed
-- Log: ROLLBACK_MARS_1049_GGMICHALSKI_20251125_092742.log
-- INSTALL TEST: All packages deployed to v3.2.1/v2.1.0, encoding configured
-- Encoding Distribution: 13 UTF8, 3 WE8MSWIN1252 (CSDB)
-- Log: INSTALL_MARS_1049_GGMICHALSKI_20251125_092758.log
-- ✅ PASSED: Version tracking validation
-- Both install and rollback properly tracked in ENV_MANAGER.TRACK_PACKAGE_VERSION
-- Complete audit trail maintained for compliance
-- ✅ PASSED: Dynamic spool logging
-- Automatic unique log file generation with PDB name and timestamp
-- Complete installation/rollback output captured for troubleshooting
```
---
## 🔄 Rollback Capability
Complete rollback capability available if needed:
### Rollback Process
```sql
-- Execute complete rollback
@@rollback_mars1049.sql
```
### What Rollback Does
1. **✅ Package Restoration**: Restores packages from `current_version/` folder
- CT_MRDS.FILE_MANAGER → v3.2.0 (without pEncoding)
- ODS.FILE_MANAGER_ODS → v2.0.0 (without pEncoding)
2. **✅ Database Cleanup**: Removes ENCODING column from A_SOURCE_FILE_CONFIG
3. **✅ Version Tracking**: Records rollback in ENV_MANAGER tracking system
4. **✅ Audit Logging**: Creates timestamped log file for compliance
5. **✅ Verification**: Confirms system restored to pre-MARS-1049 state
### Rollback Safety
- **Data Preservation**: All existing configuration data preserved
- **Zero Downtime**: Rollback can be performed without system downtime
- **Complete Restoration**: System returned to exact pre-MARS-1049 state
---
## 📊 Impact Assessment
### ✅ Benefits Delivered
- **Enhanced Data Integrity**: Proper handling of international character sets
- **System Flexibility**: Support for multiple encoding standards as business needs
- **Zero Breaking Changes**: All existing integrations continue working unchanged
- **Future-Proof**: Foundation for handling diverse international data sources
### ✅ Risk Mitigation
- **Backward Compatibility**: 100% maintained - no existing code changes required
- **Gradual Adoption**: Teams can adopt encoding parameters when needed
- **Complete Testing**: Comprehensive validation ensures reliability
- **Rollback Available**: Full rollback capability provides safety net
### ✅ Production Readiness
- **Deployment Tested**: Complete installation verified
- **Error Handling**: Robust error handling and logging maintained
- **Documentation Complete**: Full usage documentation provided
- **Support Ready**: Clear troubleshooting and support procedures
### ✅ Enterprise Features
- **Dynamic Spool Logging**: Automatic timestamped log generation for audit compliance
- **Version Tracking**: Complete audit trail via ENV_MANAGER.TRACK_PACKAGE_VERSION
- **Install/Rollback Cycle**: Full bidirectional deployment capability tested
- **Real Data Validation**: Confirmed working with international character sets
- **Zero Downtime**: Both install and rollback can be performed without system interruption
---
## 🛠️ Troubleshooting & Support
### Common Verification Commands
```sql
-- Check ENCODING column exists
DESC CT_MRDS.A_SOURCE_FILE_CONFIG;
-- Verify package versions
SELECT CT_MRDS.FILE_MANAGER.GET_VERSION() FROM DUAL; -- Should return: 3.2.1
SELECT ODS.FILE_MANAGER_ODS.GET_VERSION() FROM DUAL; -- Should return: 2.1.0
-- Check for compilation errors
SELECT * FROM USER_ERRORS WHERE NAME LIKE 'FILE_MANAGER%';
-- Test basic encoding functionality
BEGIN
ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(
'TEST_ENCODING_TABLE',
'CT_ET_TEMPLATES.SAMPLE_TEMPLATE',
'test/encoding/path',
CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
NULL, ',', 'UTF-8'
);
END;
/
```
### Error Resolution
- **Compilation Errors**: Check package dependencies and privileges
- **Encoding Errors**: Verify encoding name against Oracle supported character sets
- **External Table Issues**: Check JSON format generation and DBMS_CLOUD access
---
## 📞 Implementation Team & Support
**Lead Developer**: Grzegorz Michalski
**Implementation Date**: November 24, 2025
**Production Testing**: November 25, 2025
**Review Status**: ✅ Comprehensive validation and production testing completed
**Production Ready**: ✅ Fully tested and deployment ready
**Documentation Version**: 2.0.0 (Consolidated)
**Last Updated**: November 25, 2025
---
## 🎉 Implementation Success Summary
MARS-1049 CSV Encoding Support has been **successfully implemented and fully validated**:
-**Database Structure**: ENCODING column added to A_SOURCE_FILE_CONFIG
-**Package Updates**: Both FILE_MANAGER and FILE_MANAGER_ODS updated with encoding support
-**Backward Compatibility**: 100% maintained - no breaking changes
-**Testing**: Comprehensive validation completed for all scenarios
-**Real Data Testing**: Confirmed with CSDB data containing Turkish characters
-**Install/Rollback Cycle**: Complete bidirectional deployment tested and validated
-**Documentation**: Complete usage and deployment documentation provided
-**Enterprise Logging**: Dynamic spool and version tracking implemented
-**Rollback**: Full rollback capability available and tested
-**Production Ready**: System ready for immediate production deployment
**The feature is fully functional, production tested with real data, and confirmed working with international character sets. Complete install/rollback cycle validated. Ready for immediate production deployment.**
### ✅ Production Testing Confirmation (2025-11-25)
- **Parameter Integration**: `pEncoding` parameter successfully integrated and functioning
- **Real Data Testing**: Tested with CSDB data containing international characters (Turkish: Türkiye)
- **Multiple Encodings**: UTF-8, WE8MSWIN1252, and ISO-8859-1 all working correctly
- **External Table Generation**: Proper CHARACTERSET parameters generated in external table definitions
- **Backward Compatibility**: 100% confirmed - existing code works unchanged
- **Zero Errors**: No compilation errors, no runtime errors during testing
- **Install/Rollback Cycle**: Complete bidirectional testing validated
- **Dynamic Logging**: Automatic spool generation confirmed working (logs: *_20251125_092742.log, *_20251125_092758.log)
- **Version Tracking**: ENV_MANAGER.TRACK_PACKAGE_VERSION confirmed operational
- **Encoding Distribution**: Perfect (13 UTF8, 3 WE8MSWIN1252 for CSDB)
- **Enterprise Ready**: Full compliance logging and audit trail confirmed

View File

@@ -0,0 +1,487 @@
# MARS-1049: ENCODING Implementation in FILE_MANAGER
## Change Description
Adding `ENCODING` column to the `A_SOURCE_FILE_CONFIG` table and modifying the `FILE_MANAGER` package to support different character encodings for CSV files.
## Objective
Enable configuration of character encoding for individual source files without code modifications. The value from the `ENCODING` column will be passed as a `characterset` parameter in the formatting options of the `CREATE_EXTERNAL_TABLE` procedure.
---
## 1. DATABASE STRUCTURE MODIFICATIONS
### Adding ENCODING column
```sql
-- Add column to A_SOURCE_FILE_CONFIG table
ALTER TABLE CT_MRDS.A_SOURCE_FILE_CONFIG
ADD (ENCODING VARCHAR2(50));
-- Add column comment
COMMENT ON COLUMN CT_MRDS.A_SOURCE_FILE_CONFIG.ENCODING
IS 'Character encoding for CSV files (e.g. UTF8, WE8MSWIN1252, etc.)';
```
**Data type**: `VARCHAR2(50)` - sufficient for Oracle encoding names
**Nullable**: `YES` - defaults to NULL, database default encoding is used
**Default**: `NULL`
---
## 2. FILE_MANAGER PACKAGE MODIFICATIONS
### A. CREATE_EXTERNAL_TABLE procedure signature (main)
**BEFORE:**
```sql
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ','
)
```
**PO:**
```sql
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ',',
pEncoding IN VARCHAR2 DEFAULT NULL -- NOWY PARAMETR
)
```
### B. Wywołanie procedury CREATE_EXTERNAL_TABLE (overload)
**Lokalizacja**: Linie 499-506
**PRZED:**
```sql
CREATE_EXTERNAL_TABLE(
pTableName => vSourceFileReceived.EXTERNAL_TABLE_NAME,
pTemplateTableName => vSourceFileConfig.TEMPLATE_TABLE_NAME,
pPrefix => vSourceFileReceived.SOURCE_FILE_PREFIX_INBOX,
pBucketUri => ENV_MANAGER.gvInboxBucketUri,
pFileName => vFileName,
pDelimiter => ','
);
```
**PO:**
```sql
CREATE_EXTERNAL_TABLE(
pTableName => vSourceFileReceived.EXTERNAL_TABLE_NAME,
pTemplateTableName => vSourceFileConfig.TEMPLATE_TABLE_NAME,
pPrefix => vSourceFileReceived.SOURCE_FILE_PREFIX_INBOX,
pBucketUri => ENV_MANAGER.gvInboxBucketUri,
pFileName => vFileName,
pDelimiter => ',',
pEncoding => vSourceFileConfig.ENCODING -- NOWY PARAMETR
);
```
### C. Logika kodowania w opcjach formatowania
**Lokalizacja**: Około linii 455 w sekcji vFormat
**PRZED:**
```sql
IF pDelimiter = '|' THEN
vFormat := json_object('delimiter' VALUE '|', 'skipheaders' VALUE '1');
ELSE
vFormat := json_object('type' VALUE 'CSV', 'skipheaders' VALUE '1', 'ignoremissingcolumns' value 'true');
END IF;
```
**PO:**
```sql
-- Tworzenie podstawowego formatu
IF pDelimiter = '|' THEN
vFormat := json_object('delimiter' VALUE '|', 'skipheaders' VALUE '1');
ELSE
vFormat := json_object('type' VALUE 'CSV', 'skipheaders' VALUE '1', 'ignoremissingcolumns' value 'true');
END IF;
-- Dodanie kodowania jeśli zostało określone
IF pEncoding IS NOT NULL AND LENGTH(TRIM(pEncoding)) > 0 THEN
vFormat := JSON_MERGEPATCH(vFormat, json_object('characterset' VALUE pEncoding));
END IF;
```
---
## 3. PRZYKŁADY UŻYCIA
### Test z kodowaniem UTF-8
```sql
-- Konfiguracja dla plików z UTF-8 encoding
UPDATE CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = 'UTF8'
WHERE A_SOURCE_FILE_CONFIG_KEY = 1;
```
### Test z kodowaniem Windows-1252
```sql
-- Konfiguracja dla plików z Windows-1252 encoding
UPDATE CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = 'WE8MSWIN1252'
WHERE A_SOURCE_FILE_CONFIG_KEY = 2;
```
### Resetowanie do wartości domyślnych
```sql
-- Usunięcie kodowania (powrót do domyślnego kodowania bazy)
UPDATE CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = NULL
WHERE A_SOURCE_FILE_CONFIG_KEY = 1;
```
---
## 4. MODYFIKACJA ISTNIEJĄCEJ PROCEDURY ADD_SOURCE_FILE_CONFIG
### Rozszerzenie procedury ADD_SOURCE_FILE_CONFIG
**PRZED:**
```sql
PROCEDURE ADD_SOURCE_FILE_CONFIG(
pSourceKey IN VARCHAR2,
pSourceFileType IN VARCHAR2,
pSourceFileId IN VARCHAR2,
pSourceFileDesc IN VARCHAR2,
pSourceFileNamePattern IN VARCHAR2,
pTableId IN VARCHAR2,
pTemplateTableName IN VARCHAR2
)
```
**PO:**
```sql
PROCEDURE ADD_SOURCE_FILE_CONFIG(
pSourceKey IN VARCHAR2,
pSourceFileType IN VARCHAR2,
pSourceFileId IN VARCHAR2,
pSourceFileDesc IN VARCHAR2,
pSourceFileNamePattern IN VARCHAR2,
pTableId IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pEncoding IN VARCHAR2 DEFAULT NULL -- NOWY PARAMETR
)
```
### Modyfikacja INSERT statement w ADD_SOURCE_FILE_CONFIG
**PRZED:**
```sql
INSERT INTO CT_MRDS.A_SOURCE_FILE_CONFIG (
A_SOURCE_KEY, SOURCE_FILE_TYPE, SOURCE_FILE_ID, SOURCE_FILE_DESC,
SOURCE_FILE_NAME_PATTERN, TABLE_ID, TEMPLATE_TABLE_NAME
) VALUES (
pSourceKey, pSourceFileType, pSourceFileId, pSourceFileDesc,
pSourceFileNamePattern, pTableId, pTemplateTableName
);
```
**PO:**
```sql
INSERT INTO CT_MRDS.A_SOURCE_FILE_CONFIG (
A_SOURCE_KEY, SOURCE_FILE_TYPE, SOURCE_FILE_ID, SOURCE_FILE_DESC,
SOURCE_FILE_NAME_PATTERN, TABLE_ID, TEMPLATE_TABLE_NAME, ENCODING
) VALUES (
pSourceKey, pSourceFileType, pSourceFileId, pSourceFileDesc,
pSourceFileNamePattern, pTableId, pTemplateTableName, pEncoding
);
```
### Przykład użycia zmodyfikowanej procedury
```sql
-- Dodanie konfiguracji z kodowaniem UTF-8
CALL FILE_MANAGER.ADD_SOURCE_FILE_CONFIG(
pSourceKey => 'C2D',
pSourceFileType => 'INPUT',
pSourceFileId => 'UC_DISSEM',
pSourceFileDesc => 'UC DISSEM Metadata with UTF-8 encoding',
pSourceFileNamePattern => 'UC_NMA_DISSEM-*.csv',
pTableId => 'A_UC_DISSEM_METADATA_LOADS',
pTemplateTableName => 'CT_ET_TEMPLATES.C2D_A_UC_DISSEM_METADATA_LOADS',
pEncoding => 'UTF8'
);
-- Dodanie konfiguracji bez kodowania (jak dotychczas)
CALL FILE_MANAGER.ADD_SOURCE_FILE_CONFIG(
pSourceKey => 'LM',
pSourceFileType => 'INPUT',
pSourceFileId => 'STANDING_FACILITIES',
pSourceFileDesc => 'Standing Facilities Data',
pSourceFileNamePattern => 'SF_*.csv',
pTableId => 'STANDING_FACILITIES',
pTemplateTableName => 'CT_ET_TEMPLATES.LM_STANDING_FACILITIES'
-- pEncoding pomijamy - będzie NULL (domyślne kodowanie)
);
```
---
## 5. TESTY WALIDACYJNE
### Test 1: Podstawowa funkcjonalność
```sql
-- 1. Ustawienie kodowania UTF-8
UPDATE CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = 'UTF8'
WHERE A_SOURCE_FILE_CONFIG_KEY = 1;
-- 2. Test przetwarzania pliku
CALL FILE_MANAGER.PROCESS_SOURCE_FILE('INBOX/TEST/FILE_ID/TABLE_NAME/test_file.csv');
-- 3. Sprawdzenie logów
SELECT * FROM CT_MRDS.A_PROCESS_LOG
WHERE PROCEDURE_NAME = 'CREATE_EXTERNAL_TABLE'
ORDER BY LOG_DATE DESC;
```
### Test 2: Fallback do wartości domyślnych
```sql
-- 1. Ustawienie NULL
UPDATE CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = NULL
WHERE A_SOURCE_FILE_CONFIG_KEY = 1;
-- 2. Test przetwarzania - powinno być używane domyślne kodowanie
CALL FILE_MANAGER.PROCESS_SOURCE_FILE('INBOX/TEST/FILE_ID/TABLE_NAME/test_file.csv');
```
### Test 3: Różne kodowania
```sql
-- 1. Test z Windows-1252
UPDATE CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = 'WE8MSWIN1252'
WHERE A_SOURCE_FILE_CONFIG_KEY = 1;
-- 2. Test z UTF-8
UPDATE CT_MRDS.A_SOURCE_FILE_CONFIG
SET ENCODING = 'UTF8'
WHERE A_SOURCE_FILE_CONFIG_KEY = 2;
-- 3. Test przetwarzania obu plików
CALL FILE_MANAGER.PROCESS_SOURCE_FILE('INBOX/TEST1/FILE_ID/TABLE_NAME/test_file1.csv');
CALL FILE_MANAGER.PROCESS_SOURCE_FILE('INBOX/TEST2/FILE_ID/TABLE_NAME/test_file2.csv');
```
---
## 6. HARMONOGRAM WDROŻENIA
### Faza 1: Przygotowanie struktury (KRYTYCZNA)
1. ✅ Dodanie kolumny `ENCODING` do tabeli
2. ✅ Zaktualizowanie definicji tabeli w plikach DDL
### Faza 2: Modyfikacja pakietu (WYSOKA)
1. ⏳ Dodanie parametru do sygnatury `CREATE_EXTERNAL_TABLE`
2. ⏳ Implementacja logiki kodowania w formatowaniu JSON
3. ⏳ Aktualizacja wywołania w procedurze overload
4. ⏳ Aktualizacja parametrów logowania
### Faza 3: Testy i walidacja (ŚREDNIA)
1. ⏳ Testy jednostkowe z różnymi kodowaniami
2. ⏳ Testy integracyjne z różnymi typami plików
3. ⏳ Walidacja fallback do domyślnego kodowania
### Faza 4: Modyfikacja procedur konfiguracyjnych (NISKA)
1. ⏳ Modyfikacja `ADD_SOURCE_FILE_CONFIG` - dodanie parametru `pEncoding`
2. ⏳ Aktualizacja dokumentacji
3. ⏳ Przykłady użycia w confluence
---
## 7. ROLLBACK
W przypadku problemów można wykonać rollback:
```sql
-- Usunięcie kolumny (OSTROŻNIE - spowoduje utratę danych)
ALTER TABLE CT_MRDS.A_SOURCE_FILE_CONFIG DROP COLUMN ENCODING;
-- Przywrrócenie oryginalnej wersji pakietu FILE_MANAGER
-- (wymagane przywrrócenie z backupu)
```
---
## 8. UWAGI TECHNICZNE
### Ograniczenia
- Maksymalna długość nazwy kodowania: 50 znaków
- Obsługiwane kodowania: wszystkie wspierane przez Oracle Database
- Przykłady poprawnych nazw: `UTF8`, `WE8MSWIN1252`, `AL32UTF8`, `WE8ISO8859P1`
### Bezpieczeństwo
- Brak walidacji nazwy kodowania na poziomie aplikacji
- Oracle Database zwaliduje kodowanie podczas tworzenia external table
- Fallback do domyślnego kodowania bazy w przypadku NULL
### Wydajność
- Minimalne obciążenie - kodowanie dodawane tylko jeśli nie jest NULL
- Brak wpływu na istniejące procesy gdy kolumna jest NULL
- Używa natywnej funkcji JSON_MERGEPATCH Oracle Database
---
## 9. PRZYGOTOWANIE PACZKI INSTALACYJNEJ
### Struktura paczki MARS-1049
```
MARS_Packages/REL02/MARS-1049/
├── 01_MARS_1049_install_CT_MRDS_ADD_ENCODING_COLUMN.sql
├── 02_MARS_1049_install_CT_MRDS_FILE_MANAGER_SPEC.sql
├── 03_MARS_1049_install_CT_MRDS_FILE_MANAGER_BODY.sql
├── 04_MARS_1049_verify_ENCODING_FUNCTIONALITY.sql
├── 05_MARS_1049_track_version.sql
├── 91_MARS_1049_rollback_FILE_MANAGER_BODY.sql
├── 92_MARS_1049_rollback_FILE_MANAGER_SPEC.sql
├── 93_MARS_1049_rollback_ENCODING_COLUMN.sql
├── 94_MARS_1049_track_rollback_version.sql
├── install_mars1049.sql
├── rollback_mars1049.sql
└── README_ENCODING.md
```
### Zawartość skryptów instalacyjnych
#### 01_MARS_1049_install_CT_MRDS_ADD_ENCODING_COLUMN.sql
```sql
-- MARS-1049: Dodanie kolumny ENCODING do A_SOURCE_FILE_CONFIG
-- Autor: System Enhancement
-- Data: 2025-11-24
PROMPT Adding ENCODING column to CT_MRDS.A_SOURCE_FILE_CONFIG
ALTER TABLE CT_MRDS.A_SOURCE_FILE_CONFIG
ADD (ENCODING VARCHAR2(50));
COMMENT ON COLUMN CT_MRDS.A_SOURCE_FILE_CONFIG.ENCODING
IS 'Character encoding for CSV files (e.g. UTF8, WE8MSWIN1252, etc.)';
PROMPT ENCODING column added successfully
```
#### 02_MARS_1049_install_CT_MRDS_FILE_MANAGER_SPEC.sql
```sql
-- MARS-1049: Aktualizacja specyfikacji FILE_MANAGER - dodanie parametru pEncoding
-- Zawiera: Modyfikację sygnatury CREATE_EXTERNAL_TABLE i ADD_SOURCE_FILE_CONFIG
```
#### 04_MARS_1049_verify_ENCODING_FUNCTIONALITY.sql
```sql
-- MARS-1049: Weryfikacja funkcjonalności ENCODING
PROMPT Testing ENCODING functionality...
-- Test 1: Sprawdzenie struktury tabeli
SELECT COLUMN_NAME, DATA_TYPE, DATA_LENGTH, NULLABLE
FROM USER_TAB_COLUMNS
WHERE TABLE_NAME = 'A_SOURCE_FILE_CONFIG'
AND COLUMN_NAME = 'ENCODING';
-- Test 2: Test podstawowej funkcjonalności
INSERT INTO CT_MRDS.A_SOURCE_FILE_CONFIG (
A_SOURCE_KEY, SOURCE_FILE_TYPE, SOURCE_FILE_ID,
SOURCE_FILE_DESC, SOURCE_FILE_NAME_PATTERN,
TABLE_ID, TEMPLATE_TABLE_NAME, ENCODING
) VALUES (
'TEST', 'INPUT', 'ENCODING_TEST',
'Test ENCODING functionality', 'test_*.csv',
'TEST_TABLE', 'CT_ET_TEMPLATES.TEST_TABLE', 'UTF8'
);
-- Sprawdzenie czy rekord został dodany
SELECT A_SOURCE_FILE_CONFIG_KEY, ENCODING
FROM CT_MRDS.A_SOURCE_FILE_CONFIG
WHERE A_SOURCE_KEY = 'TEST' AND SOURCE_FILE_ID = 'ENCODING_TEST';
-- Cleanup
DELETE FROM CT_MRDS.A_SOURCE_FILE_CONFIG
WHERE A_SOURCE_KEY = 'TEST' AND SOURCE_FILE_ID = 'ENCODING_TEST';
PROMPT ENCODING functionality verification completed successfully
```
#### install_mars1049.sql (Master Install Script)
```sql
-- MARS-1049: Master Installation Script
-- CSV Encoding Support Implementation
PROMPT ================================================
PROMPT MARS-1049: Installing CSV Encoding Support
PROMPT ================================================
SPOOL install_mars1049.log
-- Faza 1: Struktura bazy danych
PROMPT Phase 1: Database Structure Changes
@@01_MARS_1049_install_CT_MRDS_ADD_ENCODING_COLUMN.sql
-- Faza 2: Pakiet FILE_MANAGER (Specyfikacja)
PROMPT Phase 2: FILE_MANAGER Package Specification
@@02_MARS_1049_install_CT_MRDS_FILE_MANAGER_SPEC.sql
-- Faza 3: Pakiet FILE_MANAGER (Ciało)
PROMPT Phase 3: FILE_MANAGER Package Body
@@03_MARS_1049_install_CT_MRDS_FILE_MANAGER_BODY.sql
-- Faza 4: Weryfikacja
PROMPT Phase 4: Functionality Verification
@@04_MARS_1049_verify_ENCODING_FUNCTIONALITY.sql
-- Faza 5: Tracking wersji
PROMPT Phase 5: Version Tracking
@@05_MARS_1049_track_version.sql
PROMPT ================================================
PROMPT MARS-1049: Installation completed successfully
PROMPT ================================================
SPOOL OFF
```
#### rollback_mars1049.sql (Master Rollback Script)
```sql
-- MARS-1049: Master Rollback Script
-- WARNING: This will remove ENCODING functionality
PROMPT ================================================
PROMPT MARS-1049: Rolling back CSV Encoding Support
PROMPT WARNING: This will remove ENCODING column and data!
PROMPT ================================================
SPOOL rollback_mars1049.log
-- Rollback w odwrotnej kolejności
@@94_MARS_1049_track_rollback_version.sql
@@93_MARS_1049_rollback_ENCODING_COLUMN.sql
@@92_MARS_1049_rollback_FILE_MANAGER_SPEC.sql
@@91_MARS_1049_rollback_FILE_MANAGER_BODY.sql
PROMPT ================================================
PROMPT MARS-1049: Rollback completed
PROMPT ================================================
SPOOL OFF
```
### Deployment Commands
```powershell
# Instalacja paczki MARS-1049
Get-Content "MARS_Packages\REL02\MARS-1049\install_mars1049.sql" | sql "CT_MRDS/Cloudpass#34@ggmichalski_high"
# W przypadku problemów - rollback
Get-Content "MARS_Packages\REL02\MARS-1049\rollback_mars1049.sql" | sql "CT_MRDS/Cloudpass#34@ggmichalski_high"
# Archiwizacja po instalacji
7z a -pMojeSuperHaslo -mhe=on MARS_1049_arch.7z MARS_Packages\REL02\MARS-1049\*.sql
```
---
## Status: GOTOWE DO IMPLEMENTACJI
**Utworzone**: 2025-11-24
**Autor**: System FILE_MANAGER Enhancement
**MARS Issue**: MARS-1049
**Priorytet**: WYSOKI

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,618 @@
create or replace PACKAGE CT_MRDS.FILE_MANAGER
AUTHID CURRENT_USER
AS
/**
* General comment for package: Please put comments for functions and procedures as shown in below example.
* It is a standard.
* The structure of comment is used by GET_PACKAGE_DOCUMENTATION function
* which returns documentation text for confluence page (to Copy-Paste it).
**/
-- Example comment:
/**
* @name EX_PROCEDURE_NAME
* @desc Procedure description
* @example select FILE_MANAGER.EX_PROCEDURE_NAME(pParameter => 129) from dual;
* @ex_rslt Example Result
**/
-- Package Version Information (Semantic Versioning: MAJOR.MINOR.PATCH)
PACKAGE_VERSION CONSTANT VARCHAR2(10) := '3.2.0';
PACKAGE_BUILD_DATE CONSTANT VARCHAR2(20) := '2025-10-22 16:30:00';
PACKAGE_AUTHOR CONSTANT VARCHAR2(100) := 'Grzegorz Michalski';
-- Version History (Latest changes first)
VERSION_HISTORY CONSTANT VARCHAR2(4000) :=
'3.2.0 (2025-10-22): Added package versioning system using centralized ENV_MANAGER functions' || CHR(13)||CHR(10) ||
'3.1.0 (2025-10-20): Enhanced PROCESS_SOURCE_FILE with 6-step validation workflow' || CHR(13)||CHR(10) ||
'3.0.0 (2025-10-15): Separated export procedures into dedicated DATA_EXPORTER package' || CHR(13)||CHR(10) ||
'2.5.0 (2025-10-10): Added DELETE_SOURCE_CASCADE for safe configuration removal' || CHR(13)||CHR(10) ||
'2.0.0 (2025-09-25): Added official path patterns support (INBOX 3-level, ODS 2-level, ARCHIVE 2-level)' || CHR(13)||CHR(10) ||
'1.0.0 (2025-09-01): Initial release with file processing and validation capabilities';
TYPE tSourceFileReceived IS RECORD
(
A_SOURCE_FILE_RECEIVED_KEY CT_MRDS.A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY%TYPE,
A_SOURCE_FILE_CONFIG_KEY CT_MRDS.A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_CONFIG_KEY%TYPE,
SOURCE_FILE_PREFIX_INBOX VARCHAR2(430),
SOURCE_FILE_PREFIX_ODS VARCHAR2(430),
SOURCE_FILE_PREFIX_QUARANTINE VARCHAR2(430),
SOURCE_FILE_PREFIX_ARCHIVE VARCHAR2(430),
SOURCE_FILE_NAME CT_MRDS.A_SOURCE_FILE_RECEIVED.SOURCE_FILE_NAME%TYPE,
RECEPTION_DATE CT_MRDS.A_SOURCE_FILE_RECEIVED.RECEPTION_DATE%TYPE,
PROCESSING_STATUS CT_MRDS.A_SOURCE_FILE_RECEIVED.PROCESSING_STATUS%TYPE,
EXTERNAL_TABLE_NAME CT_MRDS.A_SOURCE_FILE_RECEIVED.EXTERNAL_TABLE_NAME%TYPE
);
cgBL CONSTANT VARCHAR2(2) := CHR(13)||CHR(10);
vgSourceFileConfigKey PLS_INTEGER;
vgMsgTmp VARCHAR2(32000);
---------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------
/**
* @name GET_SOURCE_FILE_CONFIG
* @desc Get source file type by matching the source file name against source file type naming patterns
* or by specifying the id of a received source file.
* @example ...
* @ex_rslt "CT_MRDS.A_SOURCE_FILE_CONFIG%ROWTYPE"
**/
FUNCTION GET_SOURCE_FILE_CONFIG(pFileUri IN VARCHAR2 DEFAULT NULL
, pSourceFileReceivedKey IN NUMBER DEFAULT NULL
, pSourceFileConfigKey IN NUMBER DEFAULT NULL)
RETURN CT_MRDS.A_SOURCE_FILE_CONFIG%ROWTYPE;
/**
* @name REGISTER_SOURCE_FILE_RECEIVED
* @desc Register a newly received source file in A_SOURCE_FILE_RECEIVED table.
* This overload automatically determines source file type from the file name.
* It returns the value of A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY column for newly added record.
* @example vSourceFileReceivedKey := FILE_MANAGER.REGISTER_SOURCE_FILE_RECEIVED(pSourceFileReceivedName => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv');
* @ex_rslt 3245
**/
FUNCTION REGISTER_SOURCE_FILE_RECEIVED (
pSourceFileReceivedName IN VARCHAR2
)
RETURN PLS_INTEGER;
/**
* @name REGISTER_SOURCE_FILE_RECEIVED
* @desc Register a new new source file in A_SOURCE_FILE_RECEIVED table based on pSourceFileReceivedName and pSourceFileConfig.
* Then it returns the value of A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY column for newly added record.
* @example vSourceFileReceivedKey := FILE_MANAGER.REGISTER_SOURCE_FILE_RECEIVED(
* pSourceFileReceivedName => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv'
* ,pSourceFileConfig => ...A_SOURCE_FILE_CONFIG%ROWTYPE... );
* @ex_rslt 3245
**/
FUNCTION REGISTER_SOURCE_FILE_RECEIVED (
pSourceFileReceivedName IN VARCHAR2,
pSourceFileConfig IN CT_MRDS.A_SOURCE_FILE_CONFIG%ROWTYPE
)
RETURN PLS_INTEGER;
/**
* @name SET_SOURCE_FILE_RECEIVED_STATUS
* @desc Set status of file in A_SOURCE_FILE_RECEIVED table - PROCESSING_STATUS column
* based on A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY
* and provided value of pStatus parameter
* @example exec FILE_MANAGER.SET_SOURCE_FILE_RECEIVED_STATUS(pSourceFileReceivedKey => 377, pStatus => 'READY_FOR_INGESTION');
**/
PROCEDURE SET_SOURCE_FILE_RECEIVED_STATUS(
pSourceFileReceivedKey IN PLS_INTEGER,
pStatus IN VARCHAR2
);
/**
* @name GET_EXTERNAL_TABLE_COLUMNS
* @desc Function used to get string with all table columns definitions based on pTargetTableTemplate "TEMPLATE TABLE" name.
* It used for creating "EXTERNAL TABLE" using CREATE_EXTERNAL_TABLE procedure.
* @example select FILE_MANAGER.GET_EXTERNAL_TABLE_COLUMNS(pTargetTableTemplate => 'CT_ET_TEMPLATES.LM_STANDING_FACILITIES_HEADER') from dual;
* @ex_rslt "A_KEY" NUMBER(38,0) NOT NULL ENABLE,
* "A_WORKFLOW_HISTORY_KEY" NUMBER(38,0) NOT NULL ENABLE,
* "REV_NUMBER" NUMBER(28,0),
* "REF_DATE" DATE,
* "FREE_TEXT" VARCHAR2(1000 CHAR),
* "MLF_BS_TOTAL" NUMBER(28,10),
* "DF_BS_TOTAL" NUMBER(28,10),
* "MLF_SF_TOTAL" NUMBER(28,10),
* "DF_SF_TOTAL" NUMBER(28,10)
**/
FUNCTION GET_EXTERNAL_TABLE_COLUMNS (
pTargetTableTemplate IN VARCHAR2
)
RETURN CLOB;
/**
* @name CREATE_EXTERNAL_TABLE
* @desc A wrapper procedure for DBMS_CLOUD.CREATE_EXTERNAL_TABLE which creates External Table
* @example
* begin
* FILE_MANAGER.CREATE_EXTERNAL_TABLE(
* pTableName => 'STANDING_FACILITIES_HEADER',
* pTemplateTableName => 'CT_ET_TEMPLATES.LM_STANDING_FACILITIES_HEADER',
* pPrefix => 'ODS/LM/STANDING_FACILITIES_HEADER/',
* pBucketUri => 'https://objectstorage.eu-frankfurt-1.oraclecloud.com/n/frcnomajoc7v/b/mrds_data_tst/o/'
* pFileName => 'https://objectstorage.eu-frankfurt-1.oraclecloud.com/n/frcnomajoc7v/b/mrds_data_tst/o/ODS/LM/STANDING_FACILITIES_HEADER/*.csv',
* pDelimiter => ',',
* );
* end;
**/
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ','
);
/**
* @name CREATE_EXTERNAL_TABLE
* @desc Creates External Table for single file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* @example exec FILE_MANAGER.CREATE_EXTERNAL_TABLE(pSourceFileReceivedKey => 377);;
**/
PROCEDURE CREATE_EXTERNAL_TABLE (
pSourceFileReceivedKey IN NUMBER
);
/**
* @name VALIDATE_SOURCE_FILE_RECEIVED
* @desc A wrapper procedure for DBMS_CLOUD.VALIDATE_EXTERNAL_TABLE
* It validate External table build upon single file
* provided by pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* @example exec FILE_MANAGER.VALIDATE_SOURCE_FILE_RECEIVED(pSourceFileReceivedKey => 377);
**/
PROCEDURE VALIDATE_SOURCE_FILE_RECEIVED
(
pSourceFileReceivedKey IN NUMBER
);
/**
* @name VALIDATE_EXTERNAL_TABLE
* @desc A wrapper function for DBMS_CLOUD.VALIDATE_EXTERNAL_TABLE.
* It validates External Table provided by parameter pTableName.
* It returns: PASSED or FAILED.
* @example
* declare
* vStatus VARCHAR2(100);
* begin
* vStatus := FILE_MANAGER.VALIDATE_EXTERNAL_TABLE(pTableName => 'STANDING_FACILITIES_HEADER');
* DBMS_OUTPUT.PUT_LINE('vStatus = '||vStatus);
* end;
*
* @ex_rslt FAILED
**/
FUNCTION VALIDATE_EXTERNAL_TABLE(pTableName IN VARCHAR2)
RETURN VARCHAR2;
/**
* @name S_VALIDATE_EXTERNAL_TABLE
* @desc A function which checks if SELECT query reterns any rows.
* It trys to selects External Table provided by parameter pTableName.
* It returns: PASSED or FAILED.
* @example
* declare
* vStatus VARCHAR2(100);
* begin
* vStatus := FILE_MANAGER.S_VALIDATE_EXTERNAL_TABLE(pTableName => 'STANDING_FACILITIES_HEADER');
* DBMS_OUTPUT.PUT_LINE('vStatus = '||vStatus);
* end;
*
* @ex_rslt PASSED
**/
FUNCTION S_VALIDATE_EXTERNAL_TABLE(pTableName IN VARCHAR2)
RETURN VARCHAR2;
/**
* @name DROP_EXTERNAL_TABLE
* @desc It drops External Table for single file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* @example exec FILE_MANAGER.DROP_EXTERNAL_TABLE(pSourceFileReceivedKey => 377);
**/
PROCEDURE DROP_EXTERNAL_TABLE (
pSourceFileReceivedKey IN NUMBER
);
/**
* @name COPY_FILE
* @desc It copies file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* into destination provided by pDestination parameter.
* pDestination parameter allowed values are: 'ODS'
* @example exec FILE_MANAGER.COPY_FILE(pSourceFileReceivedKey => 377, pDestination => 'ODS');
**/
PROCEDURE COPY_FILE(
pSourceFileReceivedKey IN NUMBER,
pDestination IN VARCHAR2
);
/**
* @name MOVE_FILE
* @desc It moves file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* into destination provided by pDestination parameter.
* pDestination parameter allowed values are: 'ODS', 'QUARANTINE'
* @example exec FILE_MANAGER.MOVE_FILE(pSourceFileReceivedKey => 377, pDestination => 'ODS');
**/
PROCEDURE MOVE_FILE(
pSourceFileReceivedKey IN NUMBER,
pDestination IN VARCHAR2
);
/**
* @name DELETE_FOLDER_CONTENTS
* @desc It deletes all files from specified folder in the cloud storage.
* The procedure lists all objects in the specified folder prefix and deletes them one by one.
* pBucketArea parameter specifies which bucket to use: 'INBOX', 'DATA', 'ARCHIVE'
* pFolderPrefix parameter specifies the folder path within the bucket (e.g., 'C2D/UC_DISSEM/UC_NMA_DISSEM/')
* @example exec FILE_MANAGER.DELETE_FOLDER_CONTENTS(pBucketArea => 'INBOX', pFolderPrefix => 'C2D/UC_DISSEM/UC_NMA_DISSEM/');
**/
PROCEDURE DELETE_FOLDER_CONTENTS(
pBucketArea IN VARCHAR2,
pFolderPrefix IN VARCHAR2
);
/**
* @name PROCESS_SOURCE_FILE
* @desc It process file provided by pSourceFileReceivedName parameter.
* Ubmrella procedure that calls:
* - REGISTER_SOURCE_FILE_RECEIVED;
* - CREATE_EXTERNAL_TABLE;
* - VALIDATE_SOURCE_FILE_RECEIVED;
* - DROP_EXTERNAL_TABLE;
* - MOVE_FILE;
* @example exec FILE_MANAGER.PROCESS_SOURCE_FILE(pSourceFileReceivedName => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv');
**/
PROCEDURE PROCESS_SOURCE_FILE(pSourceFileReceivedName IN VARCHAR2)
;
/**
* @name PROCESS_SOURCE_FILE
* @desc It process file provided by pSourceFileReceivedName parameter and return processing result value.
* It returns (success/failure) => 0 / -(value).
* Ubmrella function that calls PROCESS_SOURCE_FILE procedure.
* @example
* declare
* vResult PLS_INTEGER;
* begin
* vResult := CT_MRDS.FILE_MANAGER.PROCESS_SOURCE_FILE(PSOURCEFILERECEIVEDNAME => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv');
* DBMS_OUTPUT.PUT_LINE('vResult = ' || vResult);
* end;
* @ex_rslt 0
* -20021
**/
FUNCTION PROCESS_SOURCE_FILE(pSourceFileReceivedName IN VARCHAR2)
RETURN PLS_INTEGER;
/**
* @name GET_DATE_FORMAT
* @desc Returns date format for specified template table name and column name.
* Date is taken from configuration A_COLUMN_DATE_FORMAT table.
* @example select FILE_MANAGER.GET_DATE_FORMAT(
* pTemplateTableName => 'STANDING_FACILITIES_HEADER',
* pColumnName => 'SNAPSHOT_DATE')
* from dual;
* @ex_rslt DD/MM/YYYY HH24:MI:SS
**/
FUNCTION GET_DATE_FORMAT(
pTemplateTableName IN VARCHAR2,
pColumnName IN VARCHAR2
) RETURN VARCHAR2;
/**
* @name GENERATE_EXTERNAL_TABLE_PARAMS
* @desc It builds two strings: pColumnList and pFieldList for specified Template Table name, by parameter: pTemplateTableName.
* @example
* declare
* vColumnList CLOB;
* vFieldList CLOB;
* begin
* FILE_MANAGER.GENERATE_EXTERNAL_TABLE_PARAMS (
* pTemplateTableName => 'CT_ET_TEMPLATES.LM_STANDING_FACILITIES_HEADER'
* ,pColumnList => vColumnList
* ,pFieldList => vFieldList
* );
* DBMS_OUTPUT.PUT_LINE('vColumnList = '||vColumnList);
* DBMS_OUTPUT.PUT_LINE('vFieldList = '||vFieldList);
* end;
* /
**/
PROCEDURE GENERATE_EXTERNAL_TABLE_PARAMS (
pTemplateTableName IN VARCHAR2,
pColumnList OUT CLOB,
pFieldList OUT CLOB
);
/**
* @name ADD_SOURCE
* @desc Insert a new record to A_SOURCE table.
* pSourceKey is a PRIMARY KEY value.
**/
PROCEDURE ADD_SOURCE (
pSourceKey IN CT_MRDS.A_SOURCE.A_SOURCE_KEY%TYPE,
pSourceName IN CT_MRDS.A_SOURCE.SOURCE_NAME%TYPE
);
/**
* @name DELETE_SOURCE_CASCADE
* @desc Safely deletes a SOURCE specified by pSourceKey parameter from A_SOURCE table and all dependent tables:
* - A_SOURCE_FILE_CONFIG
* - A_SOURCE_FILE_RECEIVED
* - A_COLUMN_DATE_FORMAT (only if template table is not shared with other source systems)
* The procedure checks if template tables are shared before deleting date format configurations.
* If a template table is used by multiple source systems, date formats are preserved.
* @example CALL CT_MRDS.FILE_MANAGER.DELETE_SOURCE_CASCADE(pSourceKey => 'TEST_SYS');
**/
PROCEDURE DELETE_SOURCE_CASCADE (
pSourceKey IN CT_MRDS.A_SOURCE.A_SOURCE_KEY%TYPE
);
/**
* @name GET_CONTAINER_SOURCE_FILE_CONFIG_KEY
* @desc For specified parameter pSourceFileId (A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID)
* it returns A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY for related CONTAINER record.
* @example select FILE_MANAGER.GET_CONTAINER_SOURCE_FILE_CONFIG_KEY(
* pSourceFileId => 'UC_DISSEM')
* from dual;
* @ex_rslt 126
**/
FUNCTION GET_CONTAINER_SOURCE_FILE_CONFIG_KEY (
pSourceFileId IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID%TYPE
) RETURN PLS_INTEGER;
/**
* @name GET_SOURCE_FILE_CONFIG_KEY
* @desc For specified input parameters,
* it returns A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY.
* @example select FILE_MANAGER.GET_SOURCE_FILE_CONFIG_KEY (
* pSourceFileType => 'INPUT'
* ,pSourceFileId => 'UC_DISSEM'
* ,pTableId => 'UC_NMA_DISSEM')
* from dual;
* @ex_rslt 126
**/
FUNCTION GET_SOURCE_FILE_CONFIG_KEY (
pSourceFileType IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_TYPE%TYPE DEFAULT 'INPUT'
,pSourceFileId IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID%TYPE
,pTableId IN CT_MRDS.A_SOURCE_FILE_CONFIG.TABLE_ID%TYPE
) RETURN PLS_INTEGER;
/**
* @name ADD_SOURCE_FILE_CONFIG
* @desc Insert a new record to A_SOURCE_FILE_CONFIG table.
**/
PROCEDURE ADD_SOURCE_FILE_CONFIG (
pSourceKey IN CT_MRDS.A_SOURCE_FILE_CONFIG.A_SOURCE_KEY%TYPE
,pSourceFileType IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_TYPE%TYPE
,pSourceFileId IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID%TYPE
,pSourceFileDesc IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_DESC%TYPE
,pSourceFileNamePattern IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_NAME_PATTERN%TYPE
,pTableId IN CT_MRDS.A_SOURCE_FILE_CONFIG.TABLE_ID%TYPE DEFAULT NULL
,pTemplateTableName IN CT_MRDS.A_SOURCE_FILE_CONFIG.TEMPLATE_TABLE_NAME%TYPE DEFAULT NULL
,pContainerFileKey IN CT_MRDS.A_SOURCE_FILE_CONFIG.CONTAINER_FILE_KEY%TYPE DEFAULT NULL
);
/**
* @name ADD_COLUMN_DATE_FORMAT
* @desc Insert a new record to A_COLUMN_DATE_FORMAT table.
**/
PROCEDURE ADD_COLUMN_DATE_FORMAT (
pTemplateTableName IN CT_MRDS.A_COLUMN_DATE_FORMAT.TEMPLATE_TABLE_NAME%TYPE
,pColumnName IN CT_MRDS.A_COLUMN_DATE_FORMAT.COLUMN_NAME%TYPE
,pDateFormat IN CT_MRDS.A_COLUMN_DATE_FORMAT.DATE_FORMAT%TYPE
);
/**
* @name GET_BUCKET_URI
* @desc Function used to get string with bucket http url.
* Possible input values for pBucketArea are: 'INBOX', 'ODS', 'DATA', 'ARCHIVE'
* @example select FILE_MANAGER.GET_BUCKET_URI(pBucketArea => 'ODS') from dual;
* @ex_rslt https://objectstorage.eu-frankfurt-1.oraclecloud.com/n/frcnomajoc7v/b/mrds_data_tst/o/
**/
FUNCTION GET_BUCKET_URI(pBucketArea VARCHAR2)
RETURN VARCHAR2;
/**
* @name GET_DET_SOURCE_FILE_CONFIG_INFO
* @desc Function returns details about A_SOURCE_FILE_CONFIG record
* for specified pSourceFileConfigKey (A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY).
* If pIncludeContainerInfo is <> 0 it returns additional info about related Container config record (A_SOURCE_FILE_CONFIG)
* If pIncludeColumnFormatInfo is <> 0 it returns additional info about related ColumnFormat config record (A_COLUMN_DATE_FORMAT)
* @example select FILE_MANAGER.GET_DET_SOURCE_FILE_CONFIG_INFO (
* pSourceFileConfigKey => 128
* ,pIncludeContainerInfo => 1
* ,pIncludeColumnFormatInfo => 1
* ) from dual;
* @ex_rslt
* Details about File Configuration:
* --------------------------------
* A_SOURCE_FILE_CONFIG_KEY = 128
* A_SOURCE_KEY = C2D
* ...
* --------------------------------
*
* Details about related Container Config:
* --------------------------------
* A_SOURCE_FILE_CONFIG_KEY = 126
* A_SOURCE_KEY = C2D
* ...
* --------------------------------
*
* Column Date Format config entries:
* --------------------------------
* TEMPLATE_TABLE_NAME = CT_ET_TEMPLATES.C2D_UC_MA_DISSEM
* ...
* --------------------------------
**/
FUNCTION GET_DET_SOURCE_FILE_CONFIG_INFO (
pSourceFileConfigKey IN CT_MRDS.A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY%TYPE
,pIncludeContainerInfo IN PLS_INTEGER DEFAULT 1
,pIncludeColumnFormatInfo IN PLS_INTEGER DEFAULT 1
) RETURN VARCHAR2;
/**
* @name GET_DET_SOURCE_FILE_RECEIVED_INFO
* @desc Function returns details about A_SOURCE_FILE_RECEIVED record
* for specified pSourceFileReceivedKey (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY).
* If pIncludeConfigInfo is <> 0 it returns additional info about related Container config record (A_SOURCE_FILE_CONFIG)
* If pIncludeContainerInfo is <> 0 it returns additional info about related Container config record (A_SOURCE_FILE_CONFIG)
* If pIncludeColumnFormatInfo is <> 0 it returns additional info about related ColumnFormat config record (A_COLUMN_DATE_FORMAT)
* @example select FILE_MANAGER.GET_DET_SOURCE_FILE_RECEIVED_INFO (
* pSourceFileReceivedKey => 377
* ,pIncludeConfigInfo => 1
* ,pIncludeContainerInfo => 1
* ,pIncludeColumnFormatInfo => 1
* ) from dual;
*
**/
FUNCTION GET_DET_SOURCE_FILE_RECEIVED_INFO (
pSourceFileReceivedKey IN CT_MRDS.A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY%TYPE
,pIncludeConfigInfo IN PLS_INTEGER DEFAULT 1
,pIncludeContainerInfo IN PLS_INTEGER DEFAULT 1
,pIncludeColumnFormatInfo IN PLS_INTEGER DEFAULT 1
) RETURN VARCHAR2;
/**
* @name GET_DET_USER_LOAD_OPERATIONS
* @desc Function returns details from USER_LOAD_OPERATIONS table
* for specified pOperationId.
* @example select FILE_MANAGER.GET_DET_USER_LOAD_OPERATIONS (pOperationId => 3608) from dual;
* @ex_rslt
* Details about USER_LOAD_OPERATIONS where ID = 3608
* --------------------------------
* ID = 3608
* TYPE = VALIDATE
* SID = 31260
* SERIAL# = 52915
* START_TIME = 2025-05-20 10.08.24.436983 EUROPE/BELGRADE
* UPDATE_TIME = 2025-05-20 10.08.24.458643 EUROPE/BELGRADE
* STATUS = FAILED
* OWNER_NAME = CT_MRDS
* TABLE_NAME = STANDING_FACILITIES_HEADER
* PARTITION_NAME =
* SUBPARTITION_NAME =
* FILE_URI_LIST =
* ROWS_LOADED =
* LOGFILE_TABLE = VALIDATE$3608_LOG
* BADFILE_TABLE = VALIDATE$3608_BAD
* STATUS_TABLE =
* TEMPEXT_TABLE =
* CREDENTIAL_NAME =
* EXPIRATION_TIME = 2025-05-22 10.08.24.436983000 EUROPE/BELGRADE
* --------------------------------
**/
FUNCTION GET_DET_USER_LOAD_OPERATIONS (
pOperationId PLS_INTEGER
) RETURN VARCHAR2;
/**
* @name ANALYZE_VALIDATION_ERRORS
* @desc Wrapper function that analyzes validation errors for a source file using its received key.
* Automatically derives template schema, table name, CSV URI and validation log table
* from file metadata and calls ENV_MANAGER.ANALYZE_VALIDATION_ERRORS.
* @example SELECT FILE_MANAGER.ANALYZE_VALIDATION_ERRORS(63) FROM DUAL;
* @ex_rslt Detailed validation analysis report with column mismatches and solutions
**/
FUNCTION ANALYZE_VALIDATION_ERRORS(
pSourceFileReceivedKey IN NUMBER
) RETURN VARCHAR2;
---------------------------------------------------------------------------------------------------------------------------
-- PACKAGE VERSION MANAGEMENT FUNCTIONS
---------------------------------------------------------------------------------------------------------------------------
/**
* @name GET_VERSION
* @desc Returns the current version number of the FILE_MANAGER package.
* Uses semantic versioning format (MAJOR.MINOR.PATCH).
* @example SELECT FILE_MANAGER.GET_VERSION() FROM DUAL;
* @ex_rslt 3.2.0
**/
FUNCTION GET_VERSION RETURN VARCHAR2;
/**
* @name GET_BUILD_INFO
* @desc Returns comprehensive build information including version, build date, and author.
* Uses centralized ENV_MANAGER.GET_PACKAGE_VERSION_INFO function.
* @example SELECT FILE_MANAGER.GET_BUILD_INFO() FROM DUAL;
* @ex_rslt Package: FILE_MANAGER
* Version: 3.2.0
* Build Date: 2025-10-22 16:30:00
* Author: Grzegorz Michalski
**/
FUNCTION GET_BUILD_INFO RETURN VARCHAR2;
/**
* @name GET_VERSION_HISTORY
* @desc Returns complete version history with all releases and changes.
* Uses centralized ENV_MANAGER.FORMAT_VERSION_HISTORY function.
* @example SELECT FILE_MANAGER.GET_VERSION_HISTORY() FROM DUAL;
* @ex_rslt FILE_MANAGER Version History:
* 3.2.0 (2025-10-22): Added package versioning system...
**/
FUNCTION GET_VERSION_HISTORY RETURN VARCHAR2;
END;
/

View File

@@ -0,0 +1,97 @@
create or replace PACKAGE BODY ODS.FILE_MANAGER_ODS
AS
/**
* CREATE_EXTERNAL_TABLE - Wrapper for CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE
*/
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ','
)
IS
vParameters CT_MRDS.A_PROCESS_LOG.PROCEDURE_PARAMETERS%TYPE;
BEGIN
-- Log the start of the procedure
vParameters := CT_MRDS.ENV_MANAGER.FORMAT_PARAMETERS(
SYS.ODCIVARCHAR2LIST(
'pTableName => ''' || pTableName || '''',
'pTemplateTableName => ''' || pTemplateTableName || '''',
'pPrefix => ''' || pPrefix || '''',
'pBucketUri => ''' || pBucketUri || '''',
'pFileName => ''' || NVL(pFileName, 'NULL') || '''',
'pDelimiter => ''' || pDelimiter || ''''
)
);
CT_MRDS.ENV_MANAGER.LOG_PROCESS_EVENT('Start FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE', 'INFO', vParameters);
-- Call the original CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE procedure
-- This ensures all logic remains centralized in the original package
-- and ODS wrapper simply delegates execution with DEFINER rights
CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE(
pTableName => pTableName,
pTemplateTableName => pTemplateTableName,
pPrefix => pPrefix,
pBucketUri => pBucketUri,
pFileName => pFileName,
pDelimiter => pDelimiter
);
CT_MRDS.ENV_MANAGER.LOG_PROCESS_EVENT('End FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE', 'INFO', vParameters);
EXCEPTION
WHEN OTHERS THEN
CT_MRDS.ENV_MANAGER.LOG_PROCESS_EVENT(
'Error in ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE: ' || SQLERRM,
'ERROR',
vParameters
);
RAISE;
END CREATE_EXTERNAL_TABLE;
----------------------------------------------------------------------------------------------------
-- PACKAGE VERSION MANAGEMENT FUNCTIONS IMPLEMENTATION
----------------------------------------------------------------------------------------------------
FUNCTION GET_VERSION
RETURN VARCHAR2
IS
BEGIN
RETURN PACKAGE_VERSION;
END GET_VERSION;
----------------------------------------------------------------------------------------------------
FUNCTION GET_BUILD_INFO
RETURN VARCHAR2
IS
BEGIN
RETURN CT_MRDS.ENV_MANAGER.GET_PACKAGE_VERSION_INFO(
pPackageName => 'FILE_MANAGER_ODS',
pVersion => PACKAGE_VERSION,
pBuildDate => PACKAGE_BUILD_DATE,
pAuthor => PACKAGE_AUTHOR
);
END GET_BUILD_INFO;
----------------------------------------------------------------------------------------------------
FUNCTION GET_VERSION_HISTORY
RETURN VARCHAR2
IS
BEGIN
RETURN CT_MRDS.ENV_MANAGER.FORMAT_VERSION_HISTORY(
pPackageName => 'FILE_MANAGER_ODS',
pVersionHistory => VERSION_HISTORY
);
END GET_VERSION_HISTORY;
----------------------------------------------------------------------------------------------------
END FILE_MANAGER_ODS;
/

View File

@@ -0,0 +1,91 @@
create or replace PACKAGE ODS.FILE_MANAGER_ODS
AUTHID DEFINER
AS
/**
* FILE_MANAGER_ODS - Wrapper package for CT_MRDS.FILE_MANAGER
*
* This package serves as a wrapper for CT_MRDS.FILE_MANAGER procedures.
* The key difference is that this package uses AUTHID DEFINER instead of
* AUTHID CURRENT_USER, which means all objects will be created in the ODS
* schema regardless of which user executes the procedures.
*
* This solves the execution context issue where users need to connect as
* ODS user to use CT_MRDS.FILE_MANAGER procedures.
*/
-- Package Version Information (Semantic Versioning: MAJOR.MINOR.PATCH)
PACKAGE_VERSION CONSTANT VARCHAR2(10) := '2.0.0';
PACKAGE_BUILD_DATE CONSTANT VARCHAR2(20) := '2025-10-22 17:15:00';
PACKAGE_AUTHOR CONSTANT VARCHAR2(100) := 'Grzegorz Michalski';
-- Version History (Latest changes first)
VERSION_HISTORY CONSTANT VARCHAR2(4000) :=
'2.0.0 (2025-10-22): Added package versioning system using centralized ENV_MANAGER functions' || CHR(13)||CHR(10) ||
'1.5.0 (2025-10-12): Enhanced external table creation with official path patterns support' || CHR(13)||CHR(10) ||
'1.0.0 (2025-09-20): Initial release with AUTHID DEFINER wrapper for external table creation';
/**
* @name CREATE_EXTERNAL_TABLE
* @desc Creates external tables that can read data from Oracle Cloud Storage.
* This is a wrapper for CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE
* but uses DEFINER rights to ensure objects are created in ODS schema.
* @param pTableName - Name of the external table to create
* @param pTemplateTableName - Template table defining the structure
* @param pPrefix - Storage path prefix in Oracle Cloud Storage
* @param pBucketUri - URI of the target bucket (default: ENV_MANAGER.gvInboxBucketUri)
* @param pFileName - Specific file name (optional)
* @param pDelimiter - Field delimiter (default: ',')
* @example EXEC ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(
* 'C2D_A_UC_DISSEM_METADATA_LOADS_INBOX',
* 'CT_ET_TEMPLATES.C2D_A_UC_DISSEM_METADATA_LOADS',
* 'INBOX/C2D/UC_DISSEM/A_UC_DISSEM_METADATA_LOADS',
* CT_MRDS.ENV_MANAGER.gvInboxBucketUri
* );
*/
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ','
);
---------------------------------------------------------------------------------------------------------------------------
-- PACKAGE VERSION MANAGEMENT FUNCTIONS
---------------------------------------------------------------------------------------------------------------------------
/**
* @name GET_VERSION
* @desc Returns the current version number of the FILE_MANAGER_ODS package.
* Uses semantic versioning format (MAJOR.MINOR.PATCH).
* @example SELECT FILE_MANAGER_ODS.GET_VERSION() FROM DUAL;
* @ex_rslt 2.0.0
**/
FUNCTION GET_VERSION RETURN VARCHAR2;
/**
* @name GET_BUILD_INFO
* @desc Returns comprehensive build information including version, build date, and author.
* Uses centralized ENV_MANAGER.GET_PACKAGE_VERSION_INFO function.
* @example SELECT FILE_MANAGER_ODS.GET_BUILD_INFO() FROM DUAL;
* @ex_rslt Package: FILE_MANAGER_ODS
* Version: 2.0.0
* Build Date: 2025-10-22 17:15:00
* Author: Grzegorz Michalski
**/
FUNCTION GET_BUILD_INFO RETURN VARCHAR2;
/**
* @name GET_VERSION_HISTORY
* @desc Returns complete version history with all releases and changes.
* Uses centralized ENV_MANAGER.FORMAT_VERSION_HISTORY function.
* @example SELECT FILE_MANAGER_ODS.GET_VERSION_HISTORY() FROM DUAL;
* @ex_rslt FILE_MANAGER_ODS Version History:
* 2.0.0 (2025-10-22): Added package versioning system...
**/
FUNCTION GET_VERSION_HISTORY RETURN VARCHAR2;
END FILE_MANAGER_ODS;
/

View File

@@ -0,0 +1,114 @@
-- ===================================================================
-- MARS-1049 MAIN INSTALL SCRIPT: CSV Encoding Support
-- ===================================================================
-- Purpose: Complete installation of CSV encoding support in FILE_MANAGER system
-- Author: Grzegorz Michalski
-- Date: 2025-11-24
-- Version: 1.1.0
-- Dynamic spool file generation
var filename VARCHAR2(100)
BEGIN
SELECT 'INSTALL_MARS_1049_' || SUBSTR(PDB_NAME, (INSTR(PDB_NAME,'_',1)+1), (LENGTH(PDB_NAME)-INSTR(PDB_NAME,'_',1))) || '_' ||TO_CHAR(SYSDATE,'YYYYMMDD_HH24MISS')||'.log' INTO :filename from DBA_PDBS;
END;
/
column filename new_value _filename
select :filename filename from dual;
spool &_filename
--
-- IMPLEMENTATION STATUS: COMPLETED and DEPLOYED
-- - A_SOURCE_FILE_CONFIG: ENCODING VARCHAR2(50) column added
-- - CT_MRDS.FILE_MANAGER: Updated to version 3.2.1 with pEncoding parameter
-- - ODS.FILE_MANAGER_ODS: Updated to version 2.1.0 with pEncoding wrapper support
-- - JSON Implementation: Uses JSON_OBJECT due to Oracle 23c compatibility
--
-- IMPORTANT: Tests are NOT part of this installation.
-- Testing is separate and optional (see test/ directory).
--
-- DEPLOYMENT ORDER (CRITICAL):
-- 0. Grant SELECT ANY DICTIONARY to CT_MRDS (for cross-schema hash tracking)
-- 1. Database structure changes (A_SOURCE_FILE_CONFIG.ENCODING column)
-- 2. Update existing configurations with default encoding values
-- 3. CT_MRDS.FILE_MANAGER package specification
-- 4. CT_MRDS.FILE_MANAGER package body
-- 5. ODS.FILE_MANAGER_ODS package specification
-- 6. ODS.FILE_MANAGER_ODS package body
-- 7. Track package versions
-- 8. Verify all tracked packages
--
-- NOTE: Testing is separate from installation.
-- For verification and testing, run separately:
-- test/05_MARS_1049_verify_encoding_functionality.sql
-- ===================================================================
PROMPT ===============================================
PROMPT MARS-1049: CSV Encoding Support - Full Installation
PROMPT ===============================================
-- Check prerequisites
PROMPT Checking prerequisites...
SELECT USER AS CURRENT_USER FROM DUAL;
SELECT COUNT(*) AS TABLE_COUNT FROM ALL_TABLES WHERE OWNER = 'CT_MRDS' AND TABLE_NAME = 'A_SOURCE_FILE_CONFIG';
PROMPT
PROMPT Step 0: Granting permissions for cross-schema hash tracking...
PROMPT ===============================================
@@00_MARS_1049_grant_permissions.sql
PROMPT
PROMPT Step 1: Installing database structure changes...
PROMPT ===============================================
@@01_MARS_1049_install_CT_MRDS_ADD_ENCODING_COLUMN.sql
PROMPT
PROMPT Step 2: Updating existing configurations with encoding values...
PROMPT ===============================================
@@02_MARS_1049_update_CT_MRDS_ENCODING_COLUMN.sql
PROMPT
PROMPT Step 3: Installing CT_MRDS.FILE_MANAGER specification...
PROMPT ===============================================
@@new_version/FILE_MANAGER.pkg
PROMPT
PROMPT Step 4: Installing CT_MRDS.FILE_MANAGER package body...
PROMPT ===============================================
@@new_version/FILE_MANAGER.pkb
PROMPT
PROMPT Step 5: Installing ODS.FILE_MANAGER_ODS specification...
PROMPT ===============================================
@@new_version/FILE_MANAGER_ODS.pkg
PROMPT
PROMPT Step 6: Installing ODS.FILE_MANAGER_ODS package body...
PROMPT ===============================================
@@new_version/FILE_MANAGER_ODS.pkb
PROMPT
PROMPT Step 7: Tracking package versions...
PROMPT ===============================================
@@track_package_versions.sql
PROMPT
PROMPT Step 8: Verifying all tracked packages...
PROMPT ===============================================
@@verify_packages_version.sql
PROMPT
PROMPT ===============================================
PROMPT MARS-1049: Installation Complete!
PROMPT ===============================================
PROMPT
PROMPT Summary of Changes:
PROMPT - A_SOURCE_FILE_CONFIG: Added ENCODING VARCHAR2(50) column for CSV character set specification
PROMPT - A_SOURCE_FILE_CONFIG: Updated existing configurations with default encoding values (UTF8 default, WE8MSWIN1252 for CSDB)
PROMPT - CT_MRDS.FILE_MANAGER v3.2.1: Added pEncoding parameter to ADD_SOURCE_FILE_CONFIG and CREATE_EXTERNAL_TABLE
PROMPT - ODS.FILE_MANAGER_ODS v2.1.0: Updated wrapper package with pEncoding parameter delegation
PROMPT
PROMPT Installation completed successfully!
PROMPT
spool off
exit

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,633 @@
create or replace PACKAGE CT_MRDS.FILE_MANAGER
AUTHID CURRENT_USER
AS
/**
* General comment for package: Please put comments for functions and procedures as shown in below example.
* It is a standard.
* The structure of comment is used by GET_PACKAGE_DOCUMENTATION function
* which returns documentation text for confluence page (to Copy-Paste it).
**/
-- Example comment:
/**
* @name EX_PROCEDURE_NAME
* @desc Procedure description
* @example select FILE_MANAGER.EX_PROCEDURE_NAME(pParameter => 129) from dual;
* @ex_rslt Example Result
**/
-- Package Version Information (Semantic Versioning: MAJOR.MINOR.PATCH)
PACKAGE_VERSION CONSTANT VARCHAR2(10) := '3.2.1';
PACKAGE_BUILD_DATE CONSTANT VARCHAR2(20) := '2025-11-24 12:00:00';
PACKAGE_AUTHOR CONSTANT VARCHAR2(100) := 'Grzegorz Michalski';
-- Version History (Latest changes first)
VERSION_HISTORY CONSTANT VARCHAR2(4000) :=
'3.2.1 (2025-11-24): MARS-1049 - Added pEncoding parameter support for CSV character set specification' || CHR(13)||CHR(10) ||
'3.2.0 (2025-10-22): Added package versioning system using centralized ENV_MANAGER functions' || CHR(13)||CHR(10) ||
'3.1.0 (2025-10-20): Enhanced PROCESS_SOURCE_FILE with 6-step validation workflow' || CHR(13)||CHR(10) ||
'3.0.0 (2025-10-15): Separated export procedures into dedicated DATA_EXPORTER package' || CHR(13)||CHR(10) ||
'2.5.0 (2025-10-10): Added DELETE_SOURCE_CASCADE for safe configuration removal' || CHR(13)||CHR(10) ||
'2.0.0 (2025-09-25): Added official path patterns support (INBOX 3-level, ODS 2-level, ARCHIVE 2-level)' || CHR(13)||CHR(10) ||
'1.0.0 (2025-09-01): Initial release with file processing and validation capabilities';
TYPE tSourceFileReceived IS RECORD
(
A_SOURCE_FILE_RECEIVED_KEY CT_MRDS.A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY%TYPE,
A_SOURCE_FILE_CONFIG_KEY CT_MRDS.A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_CONFIG_KEY%TYPE,
SOURCE_FILE_PREFIX_INBOX VARCHAR2(430),
SOURCE_FILE_PREFIX_ODS VARCHAR2(430),
SOURCE_FILE_PREFIX_QUARANTINE VARCHAR2(430),
SOURCE_FILE_PREFIX_ARCHIVE VARCHAR2(430),
SOURCE_FILE_NAME CT_MRDS.A_SOURCE_FILE_RECEIVED.SOURCE_FILE_NAME%TYPE,
RECEPTION_DATE CT_MRDS.A_SOURCE_FILE_RECEIVED.RECEPTION_DATE%TYPE,
PROCESSING_STATUS CT_MRDS.A_SOURCE_FILE_RECEIVED.PROCESSING_STATUS%TYPE,
EXTERNAL_TABLE_NAME CT_MRDS.A_SOURCE_FILE_RECEIVED.EXTERNAL_TABLE_NAME%TYPE
);
cgBL CONSTANT VARCHAR2(2) := CHR(13)||CHR(10);
vgSourceFileConfigKey PLS_INTEGER;
vgMsgTmp VARCHAR2(32000);
---------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------
/**
* @name GET_SOURCE_FILE_CONFIG
* @desc Get source file type by matching the source file name against source file type naming patterns
* or by specifying the id of a received source file.
* @example ...
* @ex_rslt "CT_MRDS.A_SOURCE_FILE_CONFIG%ROWTYPE"
**/
FUNCTION GET_SOURCE_FILE_CONFIG(pFileUri IN VARCHAR2 DEFAULT NULL
, pSourceFileReceivedKey IN NUMBER DEFAULT NULL
, pSourceFileConfigKey IN NUMBER DEFAULT NULL)
RETURN CT_MRDS.A_SOURCE_FILE_CONFIG%ROWTYPE;
/**
* @name REGISTER_SOURCE_FILE_RECEIVED
* @desc Register a newly received source file in A_SOURCE_FILE_RECEIVED table.
* This overload automatically determines source file type from the file name.
* It returns the value of A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY column for newly added record.
* @example vSourceFileReceivedKey := FILE_MANAGER.REGISTER_SOURCE_FILE_RECEIVED(pSourceFileReceivedName => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv');
* @ex_rslt 3245
**/
FUNCTION REGISTER_SOURCE_FILE_RECEIVED (
pSourceFileReceivedName IN VARCHAR2
)
RETURN PLS_INTEGER;
/**
* @name REGISTER_SOURCE_FILE_RECEIVED
* @desc Register a new new source file in A_SOURCE_FILE_RECEIVED table based on pSourceFileReceivedName and pSourceFileConfig.
* Then it returns the value of A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY column for newly added record.
* @example vSourceFileReceivedKey := FILE_MANAGER.REGISTER_SOURCE_FILE_RECEIVED(
* pSourceFileReceivedName => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv'
* ,pSourceFileConfig => ...A_SOURCE_FILE_CONFIG%ROWTYPE... );
* @ex_rslt 3245
**/
FUNCTION REGISTER_SOURCE_FILE_RECEIVED (
pSourceFileReceivedName IN VARCHAR2,
pSourceFileConfig IN CT_MRDS.A_SOURCE_FILE_CONFIG%ROWTYPE
)
RETURN PLS_INTEGER;
/**
* @name SET_SOURCE_FILE_RECEIVED_STATUS
* @desc Set status of file in A_SOURCE_FILE_RECEIVED table - PROCESSING_STATUS column
* based on A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY
* and provided value of pStatus parameter
* @example exec FILE_MANAGER.SET_SOURCE_FILE_RECEIVED_STATUS(pSourceFileReceivedKey => 377, pStatus => 'READY_FOR_INGESTION');
**/
PROCEDURE SET_SOURCE_FILE_RECEIVED_STATUS(
pSourceFileReceivedKey IN PLS_INTEGER,
pStatus IN VARCHAR2
);
/**
* @name GET_EXTERNAL_TABLE_COLUMNS
* @desc Function used to get string with all table columns definitions based on pTargetTableTemplate "TEMPLATE TABLE" name.
* It used for creating "EXTERNAL TABLE" using CREATE_EXTERNAL_TABLE procedure.
* @example select FILE_MANAGER.GET_EXTERNAL_TABLE_COLUMNS(pTargetTableTemplate => 'CT_ET_TEMPLATES.LM_STANDING_FACILITIES_HEADER') from dual;
* @ex_rslt "A_KEY" NUMBER(38,0) NOT NULL ENABLE,
* "A_WORKFLOW_HISTORY_KEY" NUMBER(38,0) NOT NULL ENABLE,
* "REV_NUMBER" NUMBER(28,0),
* "REF_DATE" DATE,
* "FREE_TEXT" VARCHAR2(1000 CHAR),
* "MLF_BS_TOTAL" NUMBER(28,10),
* "DF_BS_TOTAL" NUMBER(28,10),
* "MLF_SF_TOTAL" NUMBER(28,10),
* "DF_SF_TOTAL" NUMBER(28,10)
**/
FUNCTION GET_EXTERNAL_TABLE_COLUMNS (
pTargetTableTemplate IN VARCHAR2
)
RETURN CLOB;
/**
* @name CREATE_EXTERNAL_TABLE
* @desc A wrapper procedure for DBMS_CLOUD.CREATE_EXTERNAL_TABLE which creates External Table
* MARS-1049: Added pEncoding parameter for CSV character set specification
* @param pEncoding - Character set encoding for CSV files (e.g., 'UTF8', 'WE8MSWIN1252')
* If provided, adds CHARACTERSET clause to external table definition
* @example
* begin
* FILE_MANAGER.CREATE_EXTERNAL_TABLE(
* pTableName => 'STANDING_FACILITIES_HEADER',
* pTemplateTableName => 'CT_ET_TEMPLATES.LM_STANDING_FACILITIES_HEADER',
* pPrefix => 'ODS/LM/STANDING_FACILITIES_HEADER/',
* pBucketUri => 'https://objectstorage.eu-frankfurt-1.oraclecloud.com/n/frcnomajoc7v/b/mrds_data_tst/o/',
* pFileName => NULL,
* pDelimiter => ',',
* pEncoding => 'UTF8'
* );
* end;
**/
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ',',
pEncoding IN VARCHAR2 DEFAULT NULL -- MARS-1049: NOWY PARAMETR
);
/**
* @name CREATE_EXTERNAL_TABLE
* @desc Creates External Table for single file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* @example exec FILE_MANAGER.CREATE_EXTERNAL_TABLE(pSourceFileReceivedKey => 377);;
**/
PROCEDURE CREATE_EXTERNAL_TABLE (
pSourceFileReceivedKey IN NUMBER
);
/**
* @name VALIDATE_SOURCE_FILE_RECEIVED
* @desc A wrapper procedure for DBMS_CLOUD.VALIDATE_EXTERNAL_TABLE
* It validate External table build upon single file
* provided by pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* @example exec FILE_MANAGER.VALIDATE_SOURCE_FILE_RECEIVED(pSourceFileReceivedKey => 377);
**/
PROCEDURE VALIDATE_SOURCE_FILE_RECEIVED
(
pSourceFileReceivedKey IN NUMBER
);
/**
* @name VALIDATE_EXTERNAL_TABLE
* @desc A wrapper function for DBMS_CLOUD.VALIDATE_EXTERNAL_TABLE.
* It validates External Table provided by parameter pTableName.
* It returns: PASSED or FAILED.
* @example
* declare
* vStatus VARCHAR2(100);
* begin
* vStatus := FILE_MANAGER.VALIDATE_EXTERNAL_TABLE(pTableName => 'STANDING_FACILITIES_HEADER');
* DBMS_OUTPUT.PUT_LINE('vStatus = '||vStatus);
* end;
*
* @ex_rslt FAILED
**/
FUNCTION VALIDATE_EXTERNAL_TABLE(pTableName IN VARCHAR2)
RETURN VARCHAR2;
/**
* @name S_VALIDATE_EXTERNAL_TABLE
* @desc A function which checks if SELECT query reterns any rows.
* It trys to selects External Table provided by parameter pTableName.
* It returns: PASSED or FAILED.
* @example
* declare
* vStatus VARCHAR2(100);
* begin
* vStatus := FILE_MANAGER.S_VALIDATE_EXTERNAL_TABLE(pTableName => 'STANDING_FACILITIES_HEADER');
* DBMS_OUTPUT.PUT_LINE('vStatus = '||vStatus);
* end;
*
* @ex_rslt PASSED
**/
FUNCTION S_VALIDATE_EXTERNAL_TABLE(pTableName IN VARCHAR2)
RETURN VARCHAR2;
/**
* @name DROP_EXTERNAL_TABLE
* @desc It drops External Table for single file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* @example exec FILE_MANAGER.DROP_EXTERNAL_TABLE(pSourceFileReceivedKey => 377);
**/
PROCEDURE DROP_EXTERNAL_TABLE (
pSourceFileReceivedKey IN NUMBER
);
/**
* @name COPY_FILE
* @desc It copies file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* into destination provided by pDestination parameter.
* pDestination parameter allowed values are: 'ODS'
* @example exec FILE_MANAGER.COPY_FILE(pSourceFileReceivedKey => 377, pDestination => 'ODS');
**/
PROCEDURE COPY_FILE(
pSourceFileReceivedKey IN NUMBER,
pDestination IN VARCHAR2
);
/**
* @name MOVE_FILE
* @desc It moves file provided by
* pSourceFileReceivedKey parameter (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY)
* into destination provided by pDestination parameter.
* pDestination parameter allowed values are: 'ODS', 'QUARANTINE'
* @example exec FILE_MANAGER.MOVE_FILE(pSourceFileReceivedKey => 377, pDestination => 'ODS');
**/
PROCEDURE MOVE_FILE(
pSourceFileReceivedKey IN NUMBER,
pDestination IN VARCHAR2
);
/**
* @name DELETE_FOLDER_CONTENTS
* @desc It deletes all files from specified folder in the cloud storage.
* The procedure lists all objects in the specified folder prefix and deletes them one by one.
* pBucketArea parameter specifies which bucket to use: 'INBOX', 'DATA', 'ARCHIVE'
* pFolderPrefix parameter specifies the folder path within the bucket (e.g., 'C2D/UC_DISSEM/UC_NMA_DISSEM/')
* @example exec FILE_MANAGER.DELETE_FOLDER_CONTENTS(pBucketArea => 'INBOX', pFolderPrefix => 'C2D/UC_DISSEM/UC_NMA_DISSEM/');
**/
PROCEDURE DELETE_FOLDER_CONTENTS(
pBucketArea IN VARCHAR2,
pFolderPrefix IN VARCHAR2
);
/**
* @name PROCESS_SOURCE_FILE
* @desc It process file provided by pSourceFileReceivedName parameter.
* Ubmrella procedure that calls:
* - REGISTER_SOURCE_FILE_RECEIVED;
* - CREATE_EXTERNAL_TABLE;
* - VALIDATE_SOURCE_FILE_RECEIVED;
* - DROP_EXTERNAL_TABLE;
* - MOVE_FILE;
* @example exec FILE_MANAGER.PROCESS_SOURCE_FILE(pSourceFileReceivedName => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv');
**/
PROCEDURE PROCESS_SOURCE_FILE(pSourceFileReceivedName IN VARCHAR2)
;
/**
* @name PROCESS_SOURCE_FILE
* @desc It process file provided by pSourceFileReceivedName parameter and return processing result value.
* It returns (success/failure) => 0 / -(value).
* Ubmrella function that calls PROCESS_SOURCE_FILE procedure.
* @example
* declare
* vResult PLS_INTEGER;
* begin
* vResult := CT_MRDS.FILE_MANAGER.PROCESS_SOURCE_FILE(PSOURCEFILERECEIVEDNAME => 'INBOX/C2D/UC_DISSEM/UC_NMA_DISSEM/UC_NMA_DISSEM-277740.csv');
* DBMS_OUTPUT.PUT_LINE('vResult = ' || vResult);
* end;
* @ex_rslt 0
* -20021
**/
FUNCTION PROCESS_SOURCE_FILE(pSourceFileReceivedName IN VARCHAR2)
RETURN PLS_INTEGER;
/**
* @name GET_DATE_FORMAT
* @desc Returns date format for specified template table name and column name.
* Date is taken from configuration A_COLUMN_DATE_FORMAT table.
* @example select FILE_MANAGER.GET_DATE_FORMAT(
* pTemplateTableName => 'STANDING_FACILITIES_HEADER',
* pColumnName => 'SNAPSHOT_DATE')
* from dual;
* @ex_rslt DD/MM/YYYY HH24:MI:SS
**/
FUNCTION GET_DATE_FORMAT(
pTemplateTableName IN VARCHAR2,
pColumnName IN VARCHAR2
) RETURN VARCHAR2;
/**
* @name GENERATE_EXTERNAL_TABLE_PARAMS
* @desc It builds two strings: pColumnList and pFieldList for specified Template Table name, by parameter: pTemplateTableName.
* @example
* declare
* vColumnList CLOB;
* vFieldList CLOB;
* begin
* FILE_MANAGER.GENERATE_EXTERNAL_TABLE_PARAMS (
* pTemplateTableName => 'CT_ET_TEMPLATES.LM_STANDING_FACILITIES_HEADER'
* ,pColumnList => vColumnList
* ,pFieldList => vFieldList
* );
* DBMS_OUTPUT.PUT_LINE('vColumnList = '||vColumnList);
* DBMS_OUTPUT.PUT_LINE('vFieldList = '||vFieldList);
* end;
* /
**/
PROCEDURE GENERATE_EXTERNAL_TABLE_PARAMS (
pTemplateTableName IN VARCHAR2,
pColumnList OUT CLOB,
pFieldList OUT CLOB
);
/**
* @name ADD_SOURCE
* @desc Insert a new record to A_SOURCE table.
* pSourceKey is a PRIMARY KEY value.
**/
PROCEDURE ADD_SOURCE (
pSourceKey IN CT_MRDS.A_SOURCE.A_SOURCE_KEY%TYPE,
pSourceName IN CT_MRDS.A_SOURCE.SOURCE_NAME%TYPE
);
/**
* @name DELETE_SOURCE_CASCADE
* @desc Safely deletes a SOURCE specified by pSourceKey parameter from A_SOURCE table and all dependent tables:
* - A_SOURCE_FILE_CONFIG
* - A_SOURCE_FILE_RECEIVED
* - A_COLUMN_DATE_FORMAT (only if template table is not shared with other source systems)
* The procedure checks if template tables are shared before deleting date format configurations.
* If a template table is used by multiple source systems, date formats are preserved.
* @example CALL CT_MRDS.FILE_MANAGER.DELETE_SOURCE_CASCADE(pSourceKey => 'TEST_SYS');
**/
PROCEDURE DELETE_SOURCE_CASCADE (
pSourceKey IN CT_MRDS.A_SOURCE.A_SOURCE_KEY%TYPE
);
/**
* @name GET_CONTAINER_SOURCE_FILE_CONFIG_KEY
* @desc For specified parameter pSourceFileId (A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID)
* it returns A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY for related CONTAINER record.
* @example select FILE_MANAGER.GET_CONTAINER_SOURCE_FILE_CONFIG_KEY(
* pSourceFileId => 'UC_DISSEM')
* from dual;
* @ex_rslt 126
**/
FUNCTION GET_CONTAINER_SOURCE_FILE_CONFIG_KEY (
pSourceFileId IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID%TYPE
) RETURN PLS_INTEGER;
/**
* @name GET_SOURCE_FILE_CONFIG_KEY
* @desc For specified input parameters,
* it returns A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY.
* @example select FILE_MANAGER.GET_SOURCE_FILE_CONFIG_KEY (
* pSourceFileType => 'INPUT'
* ,pSourceFileId => 'UC_DISSEM'
* ,pTableId => 'UC_NMA_DISSEM')
* from dual;
* @ex_rslt 126
**/
FUNCTION GET_SOURCE_FILE_CONFIG_KEY (
pSourceFileType IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_TYPE%TYPE DEFAULT 'INPUT'
,pSourceFileId IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID%TYPE
,pTableId IN CT_MRDS.A_SOURCE_FILE_CONFIG.TABLE_ID%TYPE
) RETURN PLS_INTEGER;
/**
* @name ADD_SOURCE_FILE_CONFIG
* @desc Insert a new record to A_SOURCE_FILE_CONFIG table.
* MARS-1049: Added pEncoding parameter for CSV character set specification.
* @param pEncoding - Character set encoding for CSV files (e.g., 'UTF8', 'WE8MSWIN1252', 'EE8ISO8859P2')
* If NULL, no CHARACTERSET clause is added to external table definitions
* @example CALL CT_MRDS.FILE_MANAGER.ADD_SOURCE_FILE_CONFIG(
* pSourceKey => 'C2D', pSourceFileType => 'INPUT',
* pSourceFileId => 'UC_DISSEM', pTableId => 'METADATA_LOADS',
* pTemplateTableName => 'CT_ET_TEMPLATES.C2D_A_UC_DISSEM_METADATA_LOADS',
* pEncoding => 'UTF8'
* );
**/
PROCEDURE ADD_SOURCE_FILE_CONFIG (
pSourceKey IN CT_MRDS.A_SOURCE_FILE_CONFIG.A_SOURCE_KEY%TYPE
,pSourceFileType IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_TYPE%TYPE
,pSourceFileId IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_ID%TYPE
,pSourceFileDesc IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_DESC%TYPE
,pSourceFileNamePattern IN CT_MRDS.A_SOURCE_FILE_CONFIG.SOURCE_FILE_NAME_PATTERN%TYPE
,pTableId IN CT_MRDS.A_SOURCE_FILE_CONFIG.TABLE_ID%TYPE DEFAULT NULL
,pTemplateTableName IN CT_MRDS.A_SOURCE_FILE_CONFIG.TEMPLATE_TABLE_NAME%TYPE DEFAULT NULL
,pContainerFileKey IN CT_MRDS.A_SOURCE_FILE_CONFIG.CONTAINER_FILE_KEY%TYPE DEFAULT NULL
,pEncoding IN CT_MRDS.A_SOURCE_FILE_CONFIG.ENCODING%TYPE DEFAULT NULL -- MARS-1049: NOWY PARAMETR
);
/**
* @name ADD_COLUMN_DATE_FORMAT
* @desc Insert a new record to A_COLUMN_DATE_FORMAT table.
**/
PROCEDURE ADD_COLUMN_DATE_FORMAT (
pTemplateTableName IN CT_MRDS.A_COLUMN_DATE_FORMAT.TEMPLATE_TABLE_NAME%TYPE
,pColumnName IN CT_MRDS.A_COLUMN_DATE_FORMAT.COLUMN_NAME%TYPE
,pDateFormat IN CT_MRDS.A_COLUMN_DATE_FORMAT.DATE_FORMAT%TYPE
);
/**
* @name GET_BUCKET_URI
* @desc Function used to get string with bucket http url.
* Possible input values for pBucketArea are: 'INBOX', 'ODS', 'DATA', 'ARCHIVE'
* @example select FILE_MANAGER.GET_BUCKET_URI(pBucketArea => 'ODS') from dual;
* @ex_rslt https://objectstorage.eu-frankfurt-1.oraclecloud.com/n/frcnomajoc7v/b/mrds_data_tst/o/
**/
FUNCTION GET_BUCKET_URI(pBucketArea VARCHAR2)
RETURN VARCHAR2;
/**
* @name GET_DET_SOURCE_FILE_CONFIG_INFO
* @desc Function returns details about A_SOURCE_FILE_CONFIG record
* for specified pSourceFileConfigKey (A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY).
* If pIncludeContainerInfo is <> 0 it returns additional info about related Container config record (A_SOURCE_FILE_CONFIG)
* If pIncludeColumnFormatInfo is <> 0 it returns additional info about related ColumnFormat config record (A_COLUMN_DATE_FORMAT)
* @example select FILE_MANAGER.GET_DET_SOURCE_FILE_CONFIG_INFO (
* pSourceFileConfigKey => 128
* ,pIncludeContainerInfo => 1
* ,pIncludeColumnFormatInfo => 1
* ) from dual;
* @ex_rslt
* Details about File Configuration:
* --------------------------------
* A_SOURCE_FILE_CONFIG_KEY = 128
* A_SOURCE_KEY = C2D
* ...
* --------------------------------
*
* Details about related Container Config:
* --------------------------------
* A_SOURCE_FILE_CONFIG_KEY = 126
* A_SOURCE_KEY = C2D
* ...
* --------------------------------
*
* Column Date Format config entries:
* --------------------------------
* TEMPLATE_TABLE_NAME = CT_ET_TEMPLATES.C2D_UC_MA_DISSEM
* ...
* --------------------------------
**/
FUNCTION GET_DET_SOURCE_FILE_CONFIG_INFO (
pSourceFileConfigKey IN CT_MRDS.A_SOURCE_FILE_CONFIG.A_SOURCE_FILE_CONFIG_KEY%TYPE
,pIncludeContainerInfo IN PLS_INTEGER DEFAULT 1
,pIncludeColumnFormatInfo IN PLS_INTEGER DEFAULT 1
) RETURN VARCHAR2;
/**
* @name GET_DET_SOURCE_FILE_RECEIVED_INFO
* @desc Function returns details about A_SOURCE_FILE_RECEIVED record
* for specified pSourceFileReceivedKey (A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY).
* If pIncludeConfigInfo is <> 0 it returns additional info about related Container config record (A_SOURCE_FILE_CONFIG)
* If pIncludeContainerInfo is <> 0 it returns additional info about related Container config record (A_SOURCE_FILE_CONFIG)
* If pIncludeColumnFormatInfo is <> 0 it returns additional info about related ColumnFormat config record (A_COLUMN_DATE_FORMAT)
* @example select FILE_MANAGER.GET_DET_SOURCE_FILE_RECEIVED_INFO (
* pSourceFileReceivedKey => 377
* ,pIncludeConfigInfo => 1
* ,pIncludeContainerInfo => 1
* ,pIncludeColumnFormatInfo => 1
* ) from dual;
*
**/
FUNCTION GET_DET_SOURCE_FILE_RECEIVED_INFO (
pSourceFileReceivedKey IN CT_MRDS.A_SOURCE_FILE_RECEIVED.A_SOURCE_FILE_RECEIVED_KEY%TYPE
,pIncludeConfigInfo IN PLS_INTEGER DEFAULT 1
,pIncludeContainerInfo IN PLS_INTEGER DEFAULT 1
,pIncludeColumnFormatInfo IN PLS_INTEGER DEFAULT 1
) RETURN VARCHAR2;
/**
* @name GET_DET_USER_LOAD_OPERATIONS
* @desc Function returns details from USER_LOAD_OPERATIONS table
* for specified pOperationId.
* @example select FILE_MANAGER.GET_DET_USER_LOAD_OPERATIONS (pOperationId => 3608) from dual;
* @ex_rslt
* Details about USER_LOAD_OPERATIONS where ID = 3608
* --------------------------------
* ID = 3608
* TYPE = VALIDATE
* SID = 31260
* SERIAL# = 52915
* START_TIME = 2025-05-20 10.08.24.436983 EUROPE/BELGRADE
* UPDATE_TIME = 2025-05-20 10.08.24.458643 EUROPE/BELGRADE
* STATUS = FAILED
* OWNER_NAME = CT_MRDS
* TABLE_NAME = STANDING_FACILITIES_HEADER
* PARTITION_NAME =
* SUBPARTITION_NAME =
* FILE_URI_LIST =
* ROWS_LOADED =
* LOGFILE_TABLE = VALIDATE$3608_LOG
* BADFILE_TABLE = VALIDATE$3608_BAD
* STATUS_TABLE =
* TEMPEXT_TABLE =
* CREDENTIAL_NAME =
* EXPIRATION_TIME = 2025-05-22 10.08.24.436983000 EUROPE/BELGRADE
* --------------------------------
**/
FUNCTION GET_DET_USER_LOAD_OPERATIONS (
pOperationId PLS_INTEGER
) RETURN VARCHAR2;
/**
* @name ANALYZE_VALIDATION_ERRORS
* @desc Wrapper function that analyzes validation errors for a source file using its received key.
* Automatically derives template schema, table name, CSV URI and validation log table
* from file metadata and calls ENV_MANAGER.ANALYZE_VALIDATION_ERRORS.
* @example SELECT FILE_MANAGER.ANALYZE_VALIDATION_ERRORS(63) FROM DUAL;
* @ex_rslt Detailed validation analysis report with column mismatches and solutions
**/
FUNCTION ANALYZE_VALIDATION_ERRORS(
pSourceFileReceivedKey IN NUMBER
) RETURN VARCHAR2;
---------------------------------------------------------------------------------------------------------------------------
-- PACKAGE VERSION MANAGEMENT FUNCTIONS
---------------------------------------------------------------------------------------------------------------------------
/**
* @name GET_VERSION
* @desc Returns the current version number of the FILE_MANAGER package.
* Uses semantic versioning format (MAJOR.MINOR.PATCH).
* @example SELECT FILE_MANAGER.GET_VERSION() FROM DUAL;
* @ex_rslt 3.2.0
**/
FUNCTION GET_VERSION RETURN VARCHAR2;
/**
* @name GET_BUILD_INFO
* @desc Returns comprehensive build information including version, build date, and author.
* Uses centralized ENV_MANAGER.GET_PACKAGE_VERSION_INFO function.
* @example SELECT FILE_MANAGER.GET_BUILD_INFO() FROM DUAL;
* @ex_rslt Package: FILE_MANAGER
* Version: 3.2.0
* Build Date: 2025-10-22 16:30:00
* Author: Grzegorz Michalski
**/
FUNCTION GET_BUILD_INFO RETURN VARCHAR2;
/**
* @name GET_VERSION_HISTORY
* @desc Returns complete version history with all releases and changes.
* Uses centralized ENV_MANAGER.FORMAT_VERSION_HISTORY function.
* @example SELECT FILE_MANAGER.GET_VERSION_HISTORY() FROM DUAL;
* @ex_rslt FILE_MANAGER Version History:
* 3.2.0 (2025-10-22): Added package versioning system...
**/
FUNCTION GET_VERSION_HISTORY RETURN VARCHAR2;
END;
/

View File

@@ -0,0 +1,118 @@
create or replace PACKAGE BODY ODS.FILE_MANAGER_ODS
AS
/**
* CREATE_EXTERNAL_TABLE - Wrapper for CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE
*/
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ',',
pEncoding IN VARCHAR2 DEFAULT NULL
)
IS
vParameters CT_MRDS.A_PROCESS_LOG.PROCEDURE_PARAMETERS%TYPE;
BEGIN
-- Log the start of the procedure
vParameters := CT_MRDS.ENV_MANAGER.FORMAT_PARAMETERS(
SYS.ODCIVARCHAR2LIST(
'pTableName => ''' || pTableName || '''',
'pTemplateTableName => ''' || pTemplateTableName || '''',
'pPrefix => ''' || pPrefix || '''',
'pBucketUri => ''' || pBucketUri || '''',
'pFileName => ''' || NVL(pFileName, 'NULL') || '''',
'pDelimiter => ''' || pDelimiter || '''',
'pEncoding => ''' || NVL(pEncoding, 'NULL') || ''''
)
);
CT_MRDS.ENV_MANAGER.LOG_PROCESS_EVENT('Start FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE', 'INFO', vParameters);
-- Call the original CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE procedure
-- This ensures all logic remains centralized in the original package
-- and ODS wrapper simply delegates execution with DEFINER rights
CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE(
pTableName => pTableName,
pTemplateTableName => pTemplateTableName,
pPrefix => pPrefix,
pBucketUri => pBucketUri,
pFileName => pFileName,
pDelimiter => pDelimiter,
pEncoding => pEncoding
);
CT_MRDS.ENV_MANAGER.LOG_PROCESS_EVENT('End FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE', 'INFO', vParameters);
EXCEPTION
WHEN OTHERS THEN
CT_MRDS.ENV_MANAGER.LOG_PROCESS_EVENT(
'Error in ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE: ' || SQLERRM,
'ERROR',
vParameters
);
RAISE;
END CREATE_EXTERNAL_TABLE;
----------------------------------------------------------------------------------------------------
-- PACKAGE VERSION MANAGEMENT FUNCTIONS IMPLEMENTATION
----------------------------------------------------------------------------------------------------
FUNCTION GET_VERSION
RETURN VARCHAR2
IS
BEGIN
RETURN PACKAGE_VERSION;
END GET_VERSION;
----------------------------------------------------------------------------------------------------
FUNCTION GET_BUILD_DATE
RETURN VARCHAR2
IS
BEGIN
RETURN PACKAGE_BUILD_DATE;
END GET_BUILD_DATE;
----------------------------------------------------------------------------------------------------
FUNCTION GET_AUTHOR
RETURN VARCHAR2
IS
BEGIN
RETURN PACKAGE_AUTHOR;
END GET_AUTHOR;
----------------------------------------------------------------------------------------------------
FUNCTION GET_BUILD_INFO
RETURN VARCHAR2
IS
BEGIN
RETURN CT_MRDS.ENV_MANAGER.GET_PACKAGE_VERSION_INFO(
pPackageName => 'FILE_MANAGER_ODS',
pVersion => PACKAGE_VERSION,
pBuildDate => PACKAGE_BUILD_DATE,
pAuthor => PACKAGE_AUTHOR
);
END GET_BUILD_INFO;
----------------------------------------------------------------------------------------------------
FUNCTION GET_VERSION_HISTORY
RETURN VARCHAR2
IS
BEGIN
RETURN CT_MRDS.ENV_MANAGER.FORMAT_VERSION_HISTORY(
pPackageName => 'FILE_MANAGER_ODS',
pVersionHistory => VERSION_HISTORY
);
END GET_VERSION_HISTORY;
----------------------------------------------------------------------------------------------------
END FILE_MANAGER_ODS;
/

View File

@@ -0,0 +1,116 @@
create or replace PACKAGE ODS.FILE_MANAGER_ODS
AUTHID DEFINER
AS
/**
* FILE_MANAGER_ODS - Wrapper package for CT_MRDS.FILE_MANAGER
*
* This package serves as a wrapper for CT_MRDS.FILE_MANAGER procedures.
* The key difference is that this package uses AUTHID DEFINER instead of
* AUTHID CURRENT_USER, which means all objects will be created in the ODS
* schema regardless of which user executes the procedures.
*
* This solves the execution context issue where users need to connect as
* ODS user to use CT_MRDS.FILE_MANAGER procedures.
*
* MARS-1049: Added pEncoding parameter support for CSV character set specification
*/
-- Package Version Information (Semantic Versioning: MAJOR.MINOR.PATCH)
PACKAGE_VERSION CONSTANT VARCHAR2(10) := '2.1.0';
PACKAGE_BUILD_DATE CONSTANT VARCHAR2(20) := '2025-11-24 11:50:00';
PACKAGE_AUTHOR CONSTANT VARCHAR2(100) := 'Grzegorz Michalski';
-- Version History (Latest changes first)
VERSION_HISTORY CONSTANT VARCHAR2(4000) :=
'2.1.0 (2025-11-24): MARS-1049 - Added pEncoding parameter support for CSV character set specification' || CHR(13)||CHR(10) ||
'2.0.0 (2025-10-22): Added package versioning system using centralized ENV_MANAGER functions' || CHR(13)||CHR(10) ||
'1.5.0 (2025-10-12): Enhanced external table creation with official path patterns support' || CHR(13)||CHR(10) ||
'1.0.0 (2025-09-20): Initial release with AUTHID DEFINER wrapper for external table creation';
/**
* @name CREATE_EXTERNAL_TABLE
* @desc Creates external tables that can read data from Oracle Cloud Storage.
* This is a wrapper for CT_MRDS.FILE_MANAGER.CREATE_EXTERNAL_TABLE
* but uses DEFINER rights to ensure objects are created in ODS schema.
*
* MARS-1049: Added support for CSV character set encoding specification
* @param pTableName - Name of the external table to create
* @param pTemplateTableName - Template table defining the structure
* @param pPrefix - Storage path prefix in Oracle Cloud Storage
* @param pBucketUri - URI of the target bucket (default: ENV_MANAGER.gvInboxBucketUri)
* @param pFileName - Specific file name (optional)
* @param pDelimiter - Field delimiter (default: ',')
* @param pEncoding - Character set encoding for CSV files (e.g., 'UTF-8', 'WE8MSWIN1252', 'EE8ISO8859P2')
* If NULL, no CHARACTERSET clause is added to external table definition
* @example EXEC ODS.FILE_MANAGER_ODS.CREATE_EXTERNAL_TABLE(
* 'C2D_A_UC_DISSEM_METADATA_LOADS_INBOX',
* 'CT_ET_TEMPLATES.C2D_A_UC_DISSEM_METADATA_LOADS',
* 'INBOX/C2D/UC_DISSEM/A_UC_DISSEM_METADATA_LOADS',
* CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
* NULL, ',', 'UTF-8'
* );
*/
PROCEDURE CREATE_EXTERNAL_TABLE (
pTableName IN VARCHAR2,
pTemplateTableName IN VARCHAR2,
pPrefix IN VARCHAR2,
pBucketUri IN VARCHAR2 DEFAULT CT_MRDS.ENV_MANAGER.gvInboxBucketUri,
pFileName IN VARCHAR2 DEFAULT NULL,
pDelimiter IN VARCHAR2 DEFAULT ',',
pEncoding IN VARCHAR2 DEFAULT NULL
);
---------------------------------------------------------------------------------------------------------------------------
-- PACKAGE VERSION MANAGEMENT FUNCTIONS
---------------------------------------------------------------------------------------------------------------------------
/**
* @name GET_VERSION
* @desc Returns the current version number of the FILE_MANAGER_ODS package.
* Uses semantic versioning format (MAJOR.MINOR.PATCH).
* @example SELECT FILE_MANAGER_ODS.GET_VERSION() FROM DUAL;
* @ex_rslt 2.1.0
**/
FUNCTION GET_VERSION RETURN VARCHAR2;
/**
* @name GET_BUILD_DATE
* @desc Returns the build date of the FILE_MANAGER_ODS package.
* @return VARCHAR2 - Build date in format 'YYYY-MM-DD HH24:MI:SS'
* @example SELECT ODS.FILE_MANAGER_ODS.GET_BUILD_DATE() FROM DUAL;
*/
FUNCTION GET_BUILD_DATE RETURN VARCHAR2;
/**
* @name GET_AUTHOR
* @desc Returns the author of the FILE_MANAGER_ODS package.
* @return VARCHAR2 - Package author name
* @example SELECT ODS.FILE_MANAGER_ODS.GET_AUTHOR() FROM DUAL;
*/
FUNCTION GET_AUTHOR RETURN VARCHAR2;
/**
* @name GET_BUILD_INFO
* @desc Returns comprehensive build information including version, build date, and author.
* Uses centralized ENV_MANAGER.GET_PACKAGE_VERSION_INFO function.
* @example SELECT FILE_MANAGER_ODS.GET_BUILD_INFO() FROM DUAL;
* @ex_rslt Package: FILE_MANAGER_ODS
* Version: 2.1.0
* Build Date: 2025-11-24 11:50:00
* Author: Grzegorz Michalski
**/
FUNCTION GET_BUILD_INFO RETURN VARCHAR2;
/**
* @name GET_VERSION_HISTORY
* @desc Returns complete version history with all releases and changes.
* Uses centralized ENV_MANAGER.FORMAT_VERSION_HISTORY function.
* @example SELECT FILE_MANAGER_ODS.GET_VERSION_HISTORY() FROM DUAL;
* @ex_rslt FILE_MANAGER_ODS Version History:
* 2.0.0 (2025-10-22): Added package versioning system...
**/
FUNCTION GET_VERSION_HISTORY RETURN VARCHAR2;
END FILE_MANAGER_ODS;
/

View File

@@ -0,0 +1,112 @@
-- ===================================================================
-- MARS-1049 ROLLBACK SCRIPT: CSV Encoding Support
-- ===================================================================
-- Purpose: Complete rollback of CSV encoding support changes
-- Author: Grzegorz Michalski
-- Date: 2025-11-25
-- Version: 1.5.0
-- Dynamic spool file generation
var filename VARCHAR2(100)
BEGIN
SELECT 'ROLLBACK_MARS_1049_' || SUBSTR(PDB_NAME, (INSTR(PDB_NAME,'_',1)+1), (LENGTH(PDB_NAME)-INSTR(PDB_NAME,'_',1))) || '_' ||TO_CHAR(SYSDATE,'YYYYMMDD_HH24MISS')||'.log' INTO :filename from DBA_PDBS;
END;
/
column filename new_value _filename
select :filename filename from dual;
spool &_filename
--
-- CURRENT IMPLEMENTATION STATUS:
-- - CT_MRDS.FILE_MANAGER: Version 3.2.1 with pEncoding parameter (deployed)
-- - ODS.FILE_MANAGER_ODS: Version 2.1.0 with pEncoding wrapper (deployed)
-- - A_SOURCE_FILE_CONFIG: ENCODING VARCHAR2(50) column (deployed)
--
-- ROLLBACK STRATEGY:
-- - Uses current_version/ folder for pre-MARS-1049 package versions
-- - Uses new_version/ folder for MARS-1049 enhanced versions (for reference)
--
-- ROLLBACK ORDER:
-- 1. Restore ODS.FILE_MANAGER_ODS package from current_version/ (version 2.0.0)
-- 2. Restore CT_MRDS.FILE_MANAGER package from current_version/ (version 3.2.0)
-- 3. Remove ENCODING column from A_SOURCE_FILE_CONFIG
-- 4. Track package versions
-- 5. Verify all tracked packages
-- 6. Revoke SELECT ANY DICTIONARY from CT_MRDS
-- ===================================================================
PROMPT ===============================================
PROMPT MARS-1049: CSV Encoding Support - Full Rollback
PROMPT ===============================================
-- Set error handling
WHENEVER SQLERROR CONTINUE
WHENEVER OSERROR CONTINUE
PROMPT
PROMPT Warning: This will remove the ENCODING column and revert all package changes.
PROMPT Make sure you have backed up your data if needed.
PROMPT
-- Step 1: Restore ODS.FILE_MANAGER_ODS package to version 2.0.0
PROMPT Step 1: Restoring ODS.FILE_MANAGER_ODS package to version 2.0.0...
PROMPT ===============================================
-- Restore ODS.FILE_MANAGER_ODS specification from current_version (before MARS-1049)
@@current_version/FILE_MANAGER_ODS.pkg
-- Restore ODS.FILE_MANAGER_ODS body from current_version (before MARS-1049)
@@current_version/FILE_MANAGER_ODS.pkb
PROMPT ODS.FILE_MANAGER_ODS package restored to version 2.0.0
-- Step 2: Restore CT_MRDS.FILE_MANAGER package to version 3.2.0
PROMPT Step 2: Restoring CT_MRDS.FILE_MANAGER package to version 3.2.0...
PROMPT ===============================================
-- Restore CT_MRDS.FILE_MANAGER specification from current_version (before MARS-1049)
@@current_version/FILE_MANAGER.pkg
-- Restore CT_MRDS.FILE_MANAGER body from current_version (before MARS-1049)
@@current_version/FILE_MANAGER.pkb
PROMPT CT_MRDS.FILE_MANAGER package restored to version 3.2.0
-- Step 3: Remove ENCODING column from A_SOURCE_FILE_CONFIG
PROMPT Step 3: Remove ENCODING column from A_SOURCE_FILE_CONFIG...
PROMPT ===============================================
@@91_MARS_1049_rollback_DROP_ENCODING_COLUMN.sql
-- Step 4: Track rollback version
PROMPT Step 4: Tracking package versions...
PROMPT ===============================================
@@track_package_versions.sql
PROMPT
PROMPT Step 5: Verifying all tracked packages...
PROMPT ===============================================
@@verify_packages_version.sql
PROMPT
PROMPT Step 6: Revoking cross-schema hash tracking permissions...
PROMPT ===============================================
@@90_MARS_1049_rollback_revoke_permissions.sql
PROMPT ===============================================
PROMPT MARS-1049: Rollback Complete!
PROMPT ===============================================
PROMPT
PROMPT Summary of Rollback Changes:
PROMPT - A_SOURCE_FILE_CONFIG: Removed ENCODING VARCHAR2(50) column
PROMPT - CT_MRDS.FILE_MANAGER: Restored to version 3.2.0 (before MARS-1049)
PROMPT - ODS.FILE_MANAGER_ODS: Restored to version 2.0.0 (before MARS-1049)
PROMPT - SELECT ANY DICTIONARY: Revoked from CT_MRDS (cross-schema tracking disabled)
PROMPT
PROMPT All MARS-1049 changes have been successfully rolled back.
PROMPT System is now in pre-MARS-1049 state.
PROMPT
spool off
exit

View File

@@ -0,0 +1,96 @@
-- ===================================================================
-- Simple Package Version Tracking Script
-- ===================================================================
-- Purpose: Track specified Oracle package versions
-- Author: Grzegorz Michalski
-- Date: 2025-11-25
-- Version: 3.1.0 - List-Based Edition
--
-- USAGE:
-- 1. Edit package list below (add/remove packages as needed)
-- 2. Include in your install/rollback script: @@track_package_versions.sql
-- ===================================================================
SET SERVEROUTPUT ON;
DECLARE
TYPE t_package_rec IS RECORD (
owner VARCHAR2(50),
package_name VARCHAR2(50),
version VARCHAR2(50)
);
TYPE t_packages IS TABLE OF t_package_rec;
TYPE t_string_array IS TABLE OF VARCHAR2(100);
-- ===================================================================
-- PACKAGE LIST - Edit this array to specify packages to track
-- ===================================================================
-- Add or remove entries as needed for your MARS issue
-- Format: 'SCHEMA.PACKAGE_NAME'
-- ===================================================================
vPackageList t_string_array := t_string_array(
'CT_MRDS.FILE_MANAGER',
'ODS.FILE_MANAGER_ODS'
);
-- ===================================================================
vPackages t_packages := t_packages();
vVersion VARCHAR2(50);
vCount NUMBER := 0;
vOwner VARCHAR2(50);
vPackageName VARCHAR2(50);
vDotPos NUMBER;
BEGIN
DBMS_OUTPUT.PUT_LINE('========================================');
DBMS_OUTPUT.PUT_LINE('Package Version Tracking');
DBMS_OUTPUT.PUT_LINE('========================================');
-- Process each package in the list
FOR i IN 1..vPackageList.COUNT LOOP
vDotPos := INSTR(vPackageList(i), '.');
IF vDotPos > 0 THEN
vOwner := SUBSTR(vPackageList(i), 1, vDotPos - 1);
vPackageName := SUBSTR(vPackageList(i), vDotPos + 1);
-- Get package version
BEGIN
EXECUTE IMMEDIATE 'SELECT ' || vOwner || '.' || vPackageName || '.GET_VERSION() FROM DUAL' INTO vVersion;
vPackages.EXTEND;
vPackages(vPackages.COUNT).owner := vOwner;
vPackages(vPackages.COUNT).package_name := vPackageName;
vPackages(vPackages.COUNT).version := vVersion;
-- Track in ENV_MANAGER
BEGIN
CT_MRDS.ENV_MANAGER.TRACK_PACKAGE_VERSION(
pPackageOwner => vOwner,
pPackageName => vPackageName,
pPackageVersion => vVersion,
pPackageBuildDate => TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'),
pPackageAuthor => 'Grzegorz Michalski'
);
vCount := vCount + 1;
EXCEPTION
WHEN OTHERS THEN NULL; -- Continue even if tracking fails
END;
EXCEPTION
WHEN OTHERS THEN NULL; -- Skip packages that fail
END;
END IF;
END LOOP;
-- Display results
IF vPackages.COUNT > 0 THEN
DBMS_OUTPUT.PUT_LINE('Packages tracked: ' || vCount || ' of ' || vPackages.COUNT);
DBMS_OUTPUT.PUT_LINE('');
FOR i IN 1..vPackages.COUNT LOOP
DBMS_OUTPUT.PUT_LINE(vPackages(i).owner || '.' || vPackages(i).package_name || ' = ' || vPackages(i).version);
END LOOP;
ELSE
DBMS_OUTPUT.PUT_LINE('No packages found in list');
END IF;
DBMS_OUTPUT.PUT_LINE('========================================');
END;
/

View File

@@ -0,0 +1,62 @@
-- ===================================================================
-- Universal Package Version Verification Script
-- ===================================================================
-- Purpose: Verify all tracked Oracle packages for code changes
-- Author: Grzegorz Michalski
-- Date: 2025-11-25
-- Version: 1.0.0
--
-- USAGE:
-- Include at the end of install/rollback scripts: @@verify_packages_version.sql
--
-- OUTPUT:
-- - List of all tracked packages with their current status
-- - OK: Package has not changed since last tracking
-- - WARNING: Package code changed without version update
-- ===================================================================
SET LINESIZE 200
SET PAGESIZE 1000
SET FEEDBACK OFF
PROMPT
PROMPT ========================================
PROMPT Package Version Verification
PROMPT ========================================
PROMPT
COLUMN PACKAGE_OWNER FORMAT A15
COLUMN PACKAGE_NAME FORMAT A20
COLUMN VERSION FORMAT A10
COLUMN STATUS FORMAT A80
SELECT
PACKAGE_OWNER,
PACKAGE_NAME,
PACKAGE_VERSION AS VERSION,
CT_MRDS.ENV_MANAGER.CHECK_PACKAGE_CHANGES(PACKAGE_OWNER, PACKAGE_NAME) AS STATUS
FROM (
SELECT
PACKAGE_OWNER,
PACKAGE_NAME,
PACKAGE_VERSION,
ROW_NUMBER() OVER (PARTITION BY PACKAGE_OWNER, PACKAGE_NAME ORDER BY TRACKING_DATE DESC) AS RN
FROM CT_MRDS.A_PACKAGE_VERSION_TRACKING
)
WHERE RN = 1
ORDER BY PACKAGE_OWNER, PACKAGE_NAME;
PROMPT
PROMPT ========================================
PROMPT Verification Complete
PROMPT ========================================
PROMPT
PROMPT Legend:
PROMPT OK - Package has not changed since last tracking
PROMPT WARNING - Package code changed without version update
PROMPT
PROMPT For detailed hash information, use:
PROMPT SELECT ENV_MANAGER.GET_PACKAGE_HASH_INFO('OWNER', 'PACKAGE') FROM DUAL;
PROMPT ========================================
SET FEEDBACK ON