Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo3y5-0002Hl-SM for pgsql-general@arkaria.postgresql.org; Wed, 04 Oct 2023 15:39:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qo3x5-000DGW-OX for pgsql-general@arkaria.postgresql.org; Wed, 04 Oct 2023 15:38:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo3x3-000DGD-UT for pgsql-general@lists.postgresql.org; Wed, 04 Oct 2023 15:38:20 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qo3x1-008B2Y-Gt for pgsql-general@lists.postgresql.org; Wed, 04 Oct 2023 15:38:17 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 29D615C040E; Wed, 4 Oct 2023 11:38:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 04 Oct 2023 11:38:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1696433894; x=1696520294; bh=NdN9xmMxa5YNweSSlUOKI9XGnRhzaPom4iL 4h1RKE40=; b=HR43zBB1jn0h3ZG3cc7Q7nw0vrqJBPyQEFPOWCmxS9bRx8YWSdV VdxXU6Ywi6guBIClN4k/dN+2sBVa8zQSSlKvCSOf+Me031U8T+cUhoRmIXCUrvVm p8T1F0LQBjM0QuLHGY8Ab3AvfOj/5Bpv+AFS/6T35QhBx9ncoxWdV6/XA/vPvhaj eiSEYzZowUs+9bnmnCgUtaxVhzj7gPvtSqFRsIDJpin3I+U401GRAv3Lquv2y2y0 UTiW1ZxNx5M8zcpWs0CinDOVtg/F/t+xcvbRrOKS6EB0u2N6jG5MjcpjqU/d1BhW 9YHZgXlog2saghrSm7p+SjtObpDBuMQ9qew== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1696433894; x=1696520294; bh=NdN9xmMxa5YNweSSlUOKI9XGnRhzaPom4iL 4h1RKE40=; b=RwykBRx5zeUfS5urmdM2FhKBUrjNHay0Eao8M3WT2Gvmin5gtNi ozHZot6VM1+8AHwDHYUSWDKKaQUtoEyJut0kgd3IkDtKUyUWC93uSj6eQeq6cObx nQhLqHe3QVF1+5BEFRmXOuMBECJ+lB4TstvM3A1EMbpagy8NiWl02QEVYxi4oZsT r+eFfud/v5NfP/HzTqGjg7N2oQAhjjwKHoV/6KC9XuoecuHXzbDOAoUrsrVHekC+ /h1cKDsnptGr/GIwsPLKnXPJxsjgsuRmpqQYpefXZpV47Md0xT8zPXDGsnlx/jh1 Th3fPOP0A4LBtTqsSC7YHAMvv2eXgGYgq/g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrgedvgdeklecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeefgeefieeutdfggfetgefgheekjeehteeileeigfet ieekjedvieeviefgheevtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 4 Oct 2023 11:38:13 -0400 (EDT) Message-ID: <3713a5a8-4ff4-476c-a9d0-d3eddbfcc343@aklaver.com> Date: Wed, 4 Oct 2023 08:38:12 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [EXT]Re: Strange error trying to import with Ora2PG To: "Johnson, Bruce E - (bjohnson)" Cc: "pgsql-general@lists.postgresql.org" References: <49CE54F2-0EA4-4EB2-AAEC-11835D5D7FB6@email.arizona.edu> <7ef07a8e-57bc-4b72-8e69-2b1649fdcf34@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/4/23 06:24, Johnson, Bruce E - (bjohnson) wrote: > That’s not it. export_schema.sh writes the scripts, and then emits a > ora2pg command to pull in the data (I've managed to do this a dozen > times so far working out how to do things. :-) > > The dates on the files in the sources directory are consistent with > that, and don’t change when I run the script. > > -rw-rw-r-- 1 johnson johnson 872 Sep 27 22:02 AHSC_SCHEDULE_ROUNDED_view.sql > -rw-rw-r-- 1 johnson johnson 817 Sep 27 22:02 COP_COLLEGE_HOUR_view.sql > -rw-rw-r-- 1 johnson johnson 628 Oct  3 17:06 > RESERVER_VISIBLE_RESTRICTION_view.sql > -rw-rw-r-- 1 johnson johnson 515 Sep 27 22:02 > RESOURCEAFFIL_WITHCODE_view.sql > -rw-rw-r-- 1 johnson johnson 535 Sep 27 22:02 UA_COLLEGE_LOOKUP_view.sql Alright. In your previous post you said "I tested the view creation with that code interactively, and it worked." Does that mean you ran: CREATE OR REPLACE VIEW reserver_visible_restriction (resource_id, resourcegroup_id, affil_id) AS select r.resource_id, rg.resourcegroup_id, a.affil_id FROM resources r, resourcegroupaffil rg, resourceaffil a where r.resource_id = a.resource_id and r.resource_id = rg.resource_id and r.requester_vis_only = '1’; in a psql session by itself? What happens if you do?: psql ... -f RESERVER_VISIBLE_RESTRICTION_view.sql When you run the import_all.sh does it show where it is pulling the scripts from? If you search the source file directory for "reserver_visible_restriction" is there another file that contains it? > > > >> On Oct 3, 2023, at 2:27 PM, Adrian Klaver > > wrote: >> >> External Email >> >> On 10/3/23 10:32, Johnson, Bruce E - (bjohnson) wrote: >>> I am trying to import an oracle schema with ora2pg and running into >>> an odd error when the import_all.sh script gets to a specific view. >>> The error is: >> >>> However when I re-run the import_all.sh script it errors out at the >>> same place with the same error (in fact the pasted error code is from >>> running the script AFTER I fixed it). The sql isn’t being cached >>> anywhere in the system is it? >> >> I'm betting that every time you run import_all.sh it rewrites the >> scripts. Pretty sure if you look at the file the creation script will >> have been rewritten to its original from. >> >>> I know that I modified the correct file. >>> It happens even if I drop the database and recreate it. >>> -- >>> Bruce Johnson >>> University of Arizona >>> College of Pharmacy >>> Information Technology Group >>> Institutions do not have opinions, merely customs >> >> -- >> Adrian Klaver >> adrian.klaver@aklaver.com >> > > -- > Bruce Johnson > University of Arizona > College of Pharmacy > Information Technology Group > > Institutions do not have opinions, merely customs > -- Adrian Klaver adrian.klaver@aklaver.com