# Nodes stopped working upon move from Node-red 3.1.0 to 3.1.3

**URL:** <https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697>\
**Category:** General\
**Created:** [13 December 2023 20:09 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697 "2023-12-13T20:09:33Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![omrid](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@omrid](https://discourse.nodered.org/u/omrid)\
**Post date:** [13 December 2023 20:09 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/1 "2023-12-13T20:09:33Z")

</div>

I upgraded my Node-red today from v3.1.0 to 3.1.3 (running on Windows), and my Oracle DB node ( **node-red-contrib-oracledb-mod** , version **0.6.3** ) stopped working.  
The underlying configuration node (connection profile) is always flagged as having an error (red triangle) even when configured correctly, and the interaction with the DB fails. Everything was working well on NR 3.1.0.  
I'm running Node JS 20.10.0 (LTS) and tested this with other Node JS versions, but problem persists.

Did anyone else encounter this or has an idea how to solve?

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [14 December 2023 09:13 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/2 "2023-12-14T09:13:27Z")

</div>

I'd suggest rolling back to 3.1.0 and see what happens

I think the command would be

```auto
npm install -g --unsafe-perm node-red@3.1.0

```

Hopefully someone will correct me if I've got that wrong

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2023 09:42 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/3 "2023-12-14T09:42:20Z")

</div>

I think that the node validation checking became more robust in 3.1.3, so check that you have valid entries for all fields in the node. If it has a config node for the database node check that too. Even if you can't see any problem, make a minor tweak in each one if you can (a name change for example) and click Done for the nodes. See if that helps.

Otherwise select the node and export it and paste it here.

I see from the node's github page that there are a number of unaddressed issues with the node, it appears to have been abandoned, so if you have ongoing problems with it you may have to look for an alternative solution.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [14 December 2023 09:50 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/4 "2023-12-14T09:50:24Z")

</div>

> [@Colin](#):
>
> I think that the node validation checking became more robust in 3.1.3, so check that you have valid entries for all fields in the node. If it has a config node for the database node check that too. Even if you can't see any problem, make a minor tweak in each one if you can (a name change for example) and click Done for the nodes. See if that helps.

In theory, the stricter checking came from explicit changes we made to individual nodes to do that checking - rather than something that would apply more generally to all nodes.

@omrid can you export an example of the node with an error and share it here? Just make sure you replace any sensitive information in the export such as urls/usernames etc.

---

<div class="post-metadata">

**Author:** ![omrid](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@omrid](https://discourse.nodered.org/u/omrid)\
**Post date:** [14 December 2023 09:59 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/5 "2023-12-14T09:59:08Z")

</div>

> [@knolleary](#):
>
> @omrid can you export an example of the node with an error and share it here? Just make sure you replace any sensitive information in the export such as urls/usernames etc.

Here is an example.  
Thanks.

```auto
[
    {
        "id": "37600d92351bfbdd",
        "type": "oracledb",
        "z": "42c9757190b9a252",
        "name": "",
        "usequery": false,
        "query": "INSERT INTO oracleTableName\n\t(fieldName1, fieldName2, Fieldname3)\n\tVALUES (\n\t\t:valueOfValuesArrayIndex0,\n\t\t:valueOfValuesArrayIndex1,\n\t\t:valueOfValuesArrayIndex2,\n\t)",
        "usemappings": false,
        "mappings": "[\n\t\"location.of.first.array.index.field.in.msg.payload\",\n\t\"location.of.second.array.index.field\",\n\t\"last_array_indexfield.in[3]\"\n]",
        "server": "60fdb07a114d21e9",
        "resultaction": "multi",
        "resultlimit": 100,
        "x": 160,
        "y": 100,
        "wires": [
            []
        ]
    },
    {
        "id": "60fdb07a114d21e9",
        "type": "oracle-server",
        "connectionname": "Test-profile",
        "tnsname": "",
        "connectiontype": "Classic",
        "instantclientpath": "C:\\Oracle\\instantclient_21_10",
        "host": "ILRNARADEMO01",
        "port": "1521",
        "reconnect": true,
        "reconnecttimeout": "5000",
        "db": "RADB"
    }
]

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2023 10:57 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/6 "2023-12-14T10:57:13Z")

</div>

That is odd, the export includes the server config node, but when I import and look in the db node the server is not there.

---

<div class="post-metadata">

**Author:** ![omrid](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@omrid](https://discourse.nodered.org/u/omrid)\
**Post date:** [14 December 2023 11:04 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/7 "2023-12-14T11:04:02Z")

</div>

Odd indeed. I just tried here, and both node & config node import correctly (with the validation error persisting)

---

<div class="post-metadata">

**Author:** ![softy2k](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/softy2k/32/23707_2.png) [@softy2k](https://discourse.nodered.org/u/softy2k)\
**Post date:** [14 December 2023 11:39 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/8 "2023-12-14T11:39:13Z")

</div>

Same issue, from 3.1.0 to 3.1.3 on `Ubuntu Oracle Cloud` with `NodeJs v18.19.0`

---

<div class="post-metadata">

**Author:** ![tonymacdonald](https://avatars.discourse-cdn.com/v4/letter/t/77aa72/32.png) [@tonymacdonald](https://discourse.nodered.org/u/tonymacdonald)\
**Post date:** [14 December 2023 15:06 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/9 "2023-12-14T15:06:47Z")

</div>

Just about to upgrade from NR 3.1.0 to 3.1.3 on a raspberry pi 4

Given this thread, is that recommended?

if so what is the recommended process for a minor upgrade.

wondering if the process mentioned here is required.

> [@tada Node-RED 3.1.3 Released](https://discourse.nodered.org/t/node-red-3-1-3-released/83512/2):
>
> After pulling the 3.1.3 version and still seeing 3.1.0 running I fixed the problem by stopping and removing the running image and then starting up fresh. Never had to do that before. man_shrugging Sorry for the noise. EDIT: Man, I'm "losin' it" even more than I thought. I've always had to do the above and even have a command alias for it alias NR-postupdate='NR-stop; NR-remove; NR-startdaemon' but completely spaced it. Taking suggestions for an institution to check into... crazy_face …

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2023 15:45 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/10 "2023-12-14T15:45:59Z")

</div>

As far as I know this is the only reported problem with 3.1.3

> [@tonymacdonald](#):
>
> if so what is the recommended process for a minor upgrade.

You can either run the install script from the docs, which will upgrade it, or you can run  
`sudo npm install -g --unsafe-perm node-red@latest`  
Then restart node red.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 December 2023 15:58 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/11 "2023-12-14T15:58:37Z")

</div>

> [@tonymacdonald](#):
>
> wondering if the process mentioned here is required.

No, that is a specific problem to do with the way Losinit manages his system.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [15 December 2023 13:11 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/12 "2023-12-15T13:11:30Z")

</div>

I've identified the specific issue with the oracle node and raised a PR against if with the fix: [Ensure port validation returns boolean by knolleary · Pull Request #37 · vtulluru/node-red-contrib-oracledb-mod · GitHub](https://github.com/vtulluru/node-red-contrib-oracledb-mod/pull/37)

---

<div class="post-metadata">

**Author:** ![omrid](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@omrid](https://discourse.nodered.org/u/omrid)\
**Post date:** [15 December 2023 21:25 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/13 "2023-12-15T21:25:09Z")

</div>

Thanks @knolleary. Does the above mean that a future Node-red fix will know how to handle the existing Oracle config node, or that this node will need to be updated to return a Boolean result?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [15 December 2023 21:47 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/14 "2023-12-15T21:47:00Z")

</div>

It requires the node to be updated, but I see (looking at the pull request link posted by Nick) that the author has already merged it into the code, which means you don't need to wait for him/her to release it, you can install direct from github by going into your .node-red folder and running  
`npm install vtulluru/node-red-contrib-oracledb-mod`  
Then restarting node-red.

---

<div class="post-metadata">

**Author:** ![omrid](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@omrid](https://discourse.nodered.org/u/omrid)\
**Post date:** [15 December 2023 23:32 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/15 "2023-12-15T23:32:56Z")

</div>

Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [13 February 2024 23:33 UTC](https://discourse.nodered.org/t/nodes-stopped-working-upon-move-from-node-red-3-1-0-to-3-1-3/83697/16 "2024-02-13T23:33:16Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.